Page History

...

<scm>
    <connection>scm:svn:http://svn.apache.org/repos/asf/incubator/wink/branches/wink-1.1-incubating</connection>
    <developerConnection>scm:svn:https://svn.apache.org/repos/asf/incubator/wink/branches/wink-1.1-incubating</developerConnection>
    <url>http://svn.apache.org/viewvc/incubator/wink/branches/wink-1.1-incubating</url>
</scm>

Note: the following steps to hand-edit the pom.xml files and .java files under wink-itests and wink-assembly are only necessary if the version references within them does not match the version you intend to release. Such a mismatch might occur if the versions were not updated prior to this release process.

Currently the wink-itest and wink-assembly modules are not tied to the top-level pom. The pom.xml files under these modules will be missed by the Maven release plugin. We need to change them by hand.

...

<version>1.1-incubating-SNAPSHOT</version>

Note: continue with the following steps only if the version does not match the version you intend to release. For example, if you are releasing 1.1-incubating, the above version is correct (yes, with -SNAPSHOT appended) and you do not need to continue with hand-editing these files.

If If, for example, the target version is 1.01-incubating-SNAPSHOT, change the tag in each of the places found in your find commands to:

<version>1.1-incubating-SNAPSHOT<incubating</version>

You can also use find and sed together to change the versions:

find wink-itests -name 'pom.xml' -type f -exec sed -i 's/1.01-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \;
find wink-itests -name '*.java' -type f -exec sed -i 's/1.01-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \;
find wink-assembly -name 'pom.xml' -type f -exec sed -i 's/1.01-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \;

Important: commit these changes to SVN!

...

• 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

Since the wink-itest and wink-assembly modules are not tied to the top-level pom and have not been modified by the maven release plugin, we need to change them by hand. Assume we are working on release 1.1-incubating.

Use find and sed together to change the versions:

find wink-itests -name 'pom.xml' -type f -exec sed -i 's/1.1-incubating-SNAPSHOT/1.1-incubating/g' {} \;
find wink-itests -name '*.java' -type f -exec sed -i 's/1.1-incubating-SNAPSHOT/1.1-incubating/g' {} \;
find wink-assembly -name 'pom.xml' -type f -exec sed -i 's/1.1-incubating-SNAPSHOT/1.1-incubating/g' {} \;

...

2. Perform the release

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

...