THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Warning |
|---|
This version is outdated! Work-in-progress! |
Content
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
| Info | ||
|---|---|---|
| ||
If needed, you can use Versions Maven Plugin to set -SNAPSHOT version in all poms, like below:
|
...
| Code Block |
|---|
svn co https://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_#_#_#_X STRUTS_#_#_#_X
|
Update version of archetypes
Edit src/site/resources/archetype-catalog.xml and change version of archetypes to current $VERSION, save and commit.
...
Tag the release by using the "{{release:prepare" goal }} goal of Maven:
| Code Block |
|---|
mvn release:prepare -Dusername=yourSvnUsername -Dpassword=yourSvnPassword -DautoVersionSubmodules=true
|
...
When prompted for the SCM tag name, follow this pattern: STRUTS_2_3_[PATCH_VERSION]
| Note |
|---|
For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run: |
...
]
...
| Note |
|---|
If you get the error message above, try to re-run mvn release:prepare -Dusername=yourSvnUsername -Dpassword=yourSvnPassword -DautoVersionSubmodules=true command again, -Dresume flag is set to true by default and the plugin will resume the release process from where it failed before. |
...
If you need to run perform again, (or in a different box), do:
| Code Block |
|---|
svngit coclone httphttps://svngit-wip-us.apache.org/repos/asf/struts/struts2/tags/.git git checkout $VERSION cd $VERSION mvn deploy site-deploy --no-plugin-updates -DperformRelease=true |
...