Page History

...

find wink-itests -name 'pom.xml' | xargs grep SNAPSHOT
find wink-itests -name '*.java' | xargs grep SNAPSHOT
find wink-assembly/apache-wink -name 'pom.xml' | xargs grep SNAPSHOT
find wink-assembly/wink-assembly-aggregatejar* -name 'pom.xml' | xargs grep SNAPSHOT

...

• Check that there are no uncommitted changes in the sources
• Check that there are no SNAPSHOT dependencies
• Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use)
• Transform the SCM information in the POM to include the final destination of the tag
• Run the project tests against the modified POMs to confirm everything is in working order
• Tag the code in the SCM with a version name (this will be prompted for)
• Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for)
  • NOTE: since we're running the release from the branch, and you want this branch name to match up with the version in the pom.xml files within the branch, use the same name on this "development version" prompt that you used on the "release version" prompt. We'll update the pom.xml files in trunk by hand after a successful release vote.
• Commit the modified POMs

You'll have to build some modules by hand to prepare your local repository for the release:perform: (wiki note: why is this needed?)

cd wink-assembly/wink-assembly-aggregatejar
mvn install -PCIBuild

2. Perform the release

Run the following maven command to build and deploy the release:

...

• Check out Wink site from https://svn.apache.org/repos/asf/incubator/wink/site
• Update Wink Java-Docs by:
  • Download & extract Java-Docs from distribution source archive
  • Create new directory under /wink/site/trunk/src/site/resources/VERSION and copy extracted Java-Docs
• Update Wink site Download page with new Wink release artifacts
• Follow instructions located under /wink/site/trunk/how-to.txt to rebuild the site

...

10. Update java and pom.xml files in trunk

...

Once the release is successful, and since we ran the release from a branch, the pom.xml files in trunk still have the old version number. You will want to update the version in all of the pom.xml files throughout the project; for example, from 1.1-incubating-SNAPSHOT to 1.1.2-incubating-SNAPSHOT.

This is easy to do with the Maven release plugin. Run the following from trunk (changing the version as appropriate, of course)

mvn --batch-mode release:update-versions -DdevelopmentVersion=1.1.2-incubating-SNAPSHOT
find wink-itests -name '*.java' -type f -exec sed -i 's/1.1-incubating-SNAPSHOT/1.1-incubating/g' {} \;

Commit your changes to SVN!

...