Page History

...

Creating the Camel Release

• Prepare env and directory structure

  Code Block
  export PROJ=apache-camel export PROJVER=<x.y.z> mkdir $HOME/$PROJ-$PROJVER mkdir $HOME/$PROJ-$PROJVER/maven2 mkdir $HOME/$PROJ-$PROJVER/maven mkdir $HOME/$PROJ-$PROJVER/site

• Grab the latest source from SVN

  Code Block
  svn co https://svn.apache.org/repos/asf/activemq/camel/trunk camel cd camel

• Change the version number in:

1. pom.xml - in the project root and all sub-projects
2. the value of <camel-version> property in the root pom.xml
3. Note: The command below will do the trick on Linux (replace for the appropriate version); use x.y.z-RCn for a release candidate.

   Code Block
   find . -name pom.xml | grep -v .svn | xargs sed -i -e s/x.y-SNAPSHOT/$PROJVER/g

   If you do this on MacOSX, you will need to:

   Code Block
   find . -name pom.xml | grep -v .svn | xargs sed -i "" -e s/x.y-SNAPSHOT/$PROJVER/g

• Let Maven build, test, package, and deploy the binaries

  Code Block
  mvn clean source:jar deploy -Drelease-repo-url=file:$HOME/$PROJ-$PROJVER/maven2 -Dm1-repo-url=file:$HOME/$PROJ-$PROJVER/maven -P release

• Tag the release using your local workspace to a new CAMEL_X_Y label

  Code Block
  svn copy ../camel https://svn.apache.org/repos/asf/activemq/camel/tags/camel-x.y.z -m "Camel x.y.z Release"

• Check that the binaries look fine.

Testing the Camel Release Candidate

...