When you are convinced that the release has been built correctly, proceed to deploy/upload all artifacts to the public repository.

Upload the Mule jars

The jar files will get deployed to repository.codehaus.org via m2's deploy goal. Don't forget that it takes approx. 3 hours for this to execute.

"mvn deploy" will not work unless you have your Codehaus credentials configured properly for m2. See the local_settings.xml template in the Mule project root. You should do this from bamboo.mulesoft.org as it is already set up.

If you are getting a "No trusted certificate found" error, you will need to install Codehaus' certificate to your JDK as explained here

Upload the distros

Unlike the jars, it is more practical to upload the distributions directly via a DAV client (see list below). Whichever tool you choose to use, you will need to log in to https://dav.codehaus.org/dist/mule/ and put the distros in the distributions directory.

DAV Clients Windows - Windows Explorer MacOS - from the Finder, "Go"/"Connect to Server..." Linux - nautilus (Win Explorer style), cadaver (FTP style), davfs2 (mounts to the FS)

If you get a "403 Forbidden" error when trying to upload the distributions, this is because the upload is taking too long and something with Codehaus' WebDAV times out. Try just uploading one artifact at a time (i.e., use "put" rather than "mput") or uploading from a machine "closer" to the Codehaus servers network-wise, such as one of MuleSource's VPN servers. If you have to "put" each file, this list may come in handy (just remember to change the versions)

(1.x only) Upload the DTDs

Upload the DTDs from core/src/main/resources and modules/spring/src/main/resources to the "dtds" directory of the Mule DAV space.

(2.x +) Upload the schemas

The easiest way to upload the schemas is to mount the Mule DAV space to a local directory and run the ListSchemas.groovy script, this will generate a set of commands to copy the schemas to your mounted DAV (effectively uploading them to Codehaus). First make sure that the schema version you want to update is correctly set in the ListSchemas.groovy file:

The script will upload the schemas to the proper locations and diff them against the checked-in version to make sure the upload was successful. However, the script does not currently support creating new schema locations.

You will get the following errors which can be safely ignored: Fatal Error pom.xml:43:46: The entity "nbsp" was referenced, but not declared. Fatal Error bus-conf.xml:18:29: The prefix "wsa" for element "wsa:addressing" is not bound.

Site build

Create a bamboo build plan running the command:

Make sure you increase the memory settings for this build under 'System Environment Variables':

Once the build is done (be patient, it can take 300 - 400 minutes), you should be able to see the results here: http://www.mulesoft.org/docs/site/<MULE_VERSION>/apidocs/index.html

Update the 'current3' link (under /var/www/html/docs/site) on the bamboo build machine to point to /var/www/html/docs/site/<MULE_VERSION>

Download

Just to be on the safe side, it's always a good idea to download the distributions and run a basic smoke test to rule out any problems during the upload.

Disable HTTP caching If this is not the first time downloading, you may need to disable HTTP caching in order to get the latest version. For wget, the --no-cache option is recommended.

Make sure that the schema upload was actually successful by downloading the schemas from their HTTP URL and comparing them to the versions on the release branch. We had issues with the davfs based upload in past releases.