...
When you followed the instructions you have modified a couple of files by now - commit them now otherwise the release process will fail.
Create the SVN tags (Manual method)
Create a clean SVN workspace for the release candidate
svn co https://svn.apache.org/repos/asf/commons/proper/<component>/trunk <component>-m.n.o-RC1
Edit the version fields in the POMs to remove the -SNAPSHOT
For example, on Windows (requires perl):
| No Format |
|---|
cd <component>-m.n.o-RC1
FOR /F "usebackq delims==" %%i IN (`dir pom.xml/s/b`) DO ^
perl -pi.bak -e "s!-SNAPSHOT</version!</version!" %%i
del pom.xml.bak/S
|
Or using Maven:
mvn versions:set -DnewVersion=3.1 -DgenerateBackupPoms=false
Edit the SCM entries in the parent POM. Note: use the final tag, without any RC suffix
Do "svn diff" and "svn st" to check that the changes are OK. These should only show changes to the POMs
Create the RC tag, by copying the tag workspace to SVN:
svn copy <component>-m.n.o-RC1 -m"Creating <component>-m.n.o-RC1 tag" https://svn.apache.org/repos/asf/commons/proper/<component>/tags/<component>-m.n.o-RC1
This should result in a new tag, containing the "trunk" code with the POM fixes only. All history is preserved.
Create the SVN tags (using Maven Release plugin)
Check that your poms will not lose content when they are rewritten during the release process.
...