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>

From the branch, run the following maven command to prepare the project for the release:

mvn release:prepare

Running mvn release:prepare will executes the following steps

• 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

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.

...

Important: commit these changes to SVN!

From the branch, run the following maven command to prepare the project for the release:

mvn release:prepare

Running mvn release:prepare will executes the following steps

• 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

2. Perform the release

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

...