Artifact Release

The following describes the steps to performing an artifact release.

1. Ensure you have your environment set up correctly. This means that you should have Maven installed and your settings.xml configured. If you haven't done this see the Environment Setup page.
2. Before you can perform a release, you must have no outstanding modifications, all code should be checked into SVN.
3. The current version in your pom.xml should be x.x-SNAPSHOT. x.x is the major and minor version of your project. Note that many projects chose to adopt the Mule versioning scheme so the version of the MuleForge project matches the version of Mule that it works with.
4. Next we're going to use Maven's release plugin. The release plugin will set the release version for the project, tag the source code, build the artifacts and deploy the artifacts and the maven site to MuleForge.
5. Open a shell and go to the root directory of the project
6. Run the following command -

   
   mvn -Dusername=ross -Dpassword=xxx release:clean release:prepare
   
   

   The username and password parameters are your login credentials for MuleForge.
   You'll be prompted with some questions -

   
   What is the release version for "mule-transport-test"?
   (org.mule.transports:mule-transport-test) 1.4.3: :
   What is SCM release tag or label for "mule-transport-test"?
   (org.mule.transports:mule-transport-test) mule-transport-test-1.4.3: :
   What is the new development version for "mule-transport-test"?
   (org.mule.transports:mule-transport-test) 1.4.4-SNAPSHOT: : 2.0.0-SNAPSHOT
   
   

   The default value is good for the first 2 questions, and depending on whether you are following the Mule versioning scheme you may want to set your own new development version.

7. Next run -

   
   mvn release:perform
   
   

The release may take a while since it will run a number of reports and upload everything to MuleForge. Once this process completes your release is done!

Troubleshooting

Out of Memory Error

If you get an out of memory error when running the release you just need an environment variable MAVEN_OPTS=-Xmx512m.

Error deploying artifact: Unsupported Protocol: 'dav'

This seems to be a bug in Maven 2.0.8. You can either downgrad to 2.0.7 or upgrade to 2.0.9 to fix the problem.