...
Code Block | ||||
---|---|---|---|---|
| ||||
<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.
...
Code Block | ||||
---|---|---|---|---|
| ||||
<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 the target version is 1.10-incubating-SNAPSHOT, change the tag in each of the places found in your find commands to:
Code Block | ||||
---|---|---|---|---|
| ||||
<version>1.1-incubating<incubating-SNAPSHOT</version> |
You can also use find and sed together to change the versions:
No Format |
---|
find wink-itests -name 'pom.xml' -type f -exec sed -i 's/1.10-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \; find wink-itests -name '*.java' -type f -exec sed -i 's/1.10-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \; find wink-assembly -name 'pom.xml' -type f -exec sed -i 's/1.10-incubating-SNAPSHOT/1.1-incubating-SNAPSHOT/g' {} \; |
Important: commit these changes to SVN!
...