Migrating MuleForge projects to 3.0

September 3 2010

2 comments 0
motif

In order to make sure that the path is straightforward and well-documented, I just finished migrating the SFTP MuleForge project from Mule ESB 2.2.1 to 3.0.  It was extremely helpful to have a good set of unit tests in the SFTP transport code.  That makes it easier to tell if your project still has all of the necessary functionality after the migration.  If you are interested in migrating your own MuleForge project, check out the following links:

Remember there are also other resources if you need assistance during your migration: the user list, our online documentation and jira.


We'd love to hear your opinion on this post


2 Responses to “Migrating MuleForge projects to 3.0”

  1. Thanks for the migration guide. However, I thought the SFTP transport was going to be rolled into Mule itself given how common of a transport it is for doing integration work. There are some pretty major bugs in it right now and I guess we’ll just have to fork the 3.x branch to get our fixes in since nobody is addressing the problems in JIRA (which can entirely kill the operating system):

    http://www.mulesoft.org/jira/browse/SFTP-35

  2. Mike,

    Thanks for your comment. I added your code to the 3.0 version of the transport:
    http://svn.muleforge.org/mule-transport-sftp/trunk/

    Let us know if it works for you by adding a comment in the jira. If you find any other issues, please file the appropriate jiras. Patches and test cases in the jira help us integrate fixes quicker.

    I don’t have any information about rolling the sftp transport into the ESB product; perhaps someone else can comment?

    Thanks!