Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Before releasing, make sure what is going to be released is fully functional. In particular, run the core/samples using the all-downloadable profile (mvn clean install -Pall-downloadable); in particular check that all containers pass all tests.

  • The Continous Integration for CARGO actually passes tests for all downloadable containers. Green ones are doing well (smile)
  • If any container is not passing, move it to the all-unstable-downloadable list.
  • Make sure all containers in the all-stable-downloadable profile pass the samplesFor non-publicly-downloadable containers (Glassfish 2.x, JRun 4.x as well as all versions of Orion/OC4J, WebLogic and WebSphere) tests need to be done on your computer.

Tagging and deploying on to the staging area



Release may take up to 4 6 hours. Make sure you have time before you start (smile)


Sometimes, the maven-release-plugin has trouble releasing the core module (the compiler seems to fail). In order to release manually, follow these steps:

  1. Go to the core/target/checkout folder
  2. Run mvn clean deploy -Drelease=true -DperformRelease=true -Pcodehaus-release in order to deploy the CARGO core artifacts to the Codehaus Nexus repository
  3. Run mvn site-deploy in order to deploy the CARGO documentation to the CARGO web site
  4. Return to the core folder and remove all *.releaseBackup and files

Sometimes, you might get a message saying Error deploying artifact: Failed to create destination WebDAV collection (directory): unable to find valid certification path to requested target, that's because the Codehaus HTTPS WebDAV servers' certificate is not installed on your computer. In this case:

  1. Download and compile the program from
  2. Execute the program java InstallCert and make it install one of the certificates. If you run the program again, it should be happy and tell you that all certificates are installed.
  3. Add the generated jssecacerts file to your $JAVA_HOME/jre/lib/security directory.


  1. Follow the guide on closing a staging repository on Codehaus Nexus and releasing a closed staging repository on Codehaus Nexusin order to release the CARGO artifacts to Maven Central.
  2. Log onto Cargo JIRA, release the current version and add the next version.
  3. Check that the Cargo wiki is up to date. Specifically, perform the following updates:
    1. Modify the status on the home page about the delivery:
    2. Modify the Home page to update the available version number and release date
    3. Modify the Maven2 Plugin Installation page to have the latest SNAPSHOT version in there
    4. Create a blog post
    5. Export the wiki to a zipped HTML file (select all pages except for the Downloads (including all subsections) page) and add it the Downloads page
    6. Move the old version to the Archived Downloads page
      • Remember to move the old documentation archive from the Downloads page to that page as well
    7. Modify the Home and Downloads pages page to update the download links, available version number, documentation and release note links
    8. Export the wiki to a zipped HTML file (select all pages except for the Downloads page) and add it the Downloads page
  4. Send an announcement email to Cargo mailing lists ... and to other relevent sites you know about. Mailing lists of some servers can also be interesting.
  5. Create a blog post
titleHow to insert using the Wiki Markup

To insert content using Wiki Markup:

  1. Edit the document in the Codehaus Confluence
  2. Clear the existing content by selecting all content and pressing delete on your keyboard
  3. On the toolbar, click Insert -> Wiki markup:
  4. Paste the wiki markup content