|Home > Guides > Contributors Guide > Creating and Signing a Distribution > Building Struts 2 - Normal release|
struts-site project (see details at the bottom of this page) and perform export:
If build will fail try again - don't use
clean, the exporter is going to update only outdated pages. After successful export, commit updated files into
Please remember to keep BOM subproject in sync -
<struts-version.version>X.X.X</struts-version.version> - must be the same as the parent pom.
Now you should be on
release/X.X.X.X branch (
git status supposed to confirm that).
Tag the release by using the "release:prepare" goal of Maven:
For a dry run, add
-DdryRun=true. If you do a dry run, use
mvn release:clean to clean up after you have looked at the output.
When prompted for the SCM tag name, follow this pattern: STRUTS_2_3_[PATCH_VERSION]
If you get an error message, try to re-run
mvn release:prepare -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.
Follow the link to get more information about performed operation by release plugin.
Follow the link to get more information about performed operation by release plugin. After this step the artifacts will be hosted by Nexus. The
-DretryFailedDeploymentCount=10 is needed when there are problems with network connection (used just in case).
If you need to run perform again, (or in a different box), do:
Next, log in to Nexus and close staging repository.
Repository is identified by user name and public IP address, so if in meantime your IP changed, a new staging repository will be created so you must drop the old one (check the dates!) - if IP is the same, artifacts will be uploaded to the same repository as first attempt.
To simplify testing, the assemblies have to be moved to the
After closing repository in Nexus, check if the release files are available from staging repository as bellow:
In order to move the assemblies login to people.apache.org and execute the following code:
After this step artifacts are available for test here https://dist.apache.org/repos/dist/dev/struts/
Send a short e-mail to email@example.com informing about the new packages and to give people enough time to test the distribution (actual bits). Wait around a week before posting Vote. If no show-stoppers reported, start a vote thread for build quality designation.
It doesn't matter if the bits will be accepted or not, development continues Switch to
release/X.X.X.X branch and execute the below command:
-n option is need to avoid tagging the release, the Maven Release plugin did that already.
develop branches should be up to date with the changes introduced by the release. As Maven bumps version and also prepares for next development cycle, but do this on the same branch (or rather
maven-release-plugin knows nothing about git-flow and branching), after finishing the release you must manually update actual version in the
master branch - without this
master branch has a proper version - it isn't the best solution and if you have better please let me know!
Do not remove the tag! It clearly indicates what was planned and it can be used as a history marker. Always used the next version number, do not redeploy the same version as it breaks Maven's policy and you will have to manually clean up Maven repository.
Post a release/quality vote to the dev list (and only the dev list). The example mail is on Sample announcements page. If the vote result is for an ASF release (i.e. not test build), update site, announce. If the vote result is for GA, push to central.
After the vote, if the distribution is being mirrored (there was a favourable release vote) move all the artefacts from
dev folder into
Remove the old files from under https://dist.apache.org/repos/dist/release/struts/ to synchronise only the latest version with peers. All the files from https://dist.apache.org/repos/dist/release/struts/ are always mirrored to http://archive.apache.org/dist/struts/. You can use the below command:
x is the previous version to remove (or one more previous to keep current and one version back).
Wait 24 hours before proceeding.
Check out site src code
jekyll serve -wyou can check the generated site at http://localhost:4000
Commit the changes and the generated content
Now the changes must be deployed to production which is basically a separated Subversion repository, you check it out with command below:
It's a good idea to keep that working copy to be used with future releases. Right now copy content of
struts-site/content folder to
struts-production folder, then commit changes. Next step is to update exported wiki pages. With current approach the pages are kept in
Checkout source of the website and export Confluence pages
Now the whole Confluence space is exported to
Checkout copy of production website (if you didn't that before)
(you can checkout just a subtree, but it's better to checkout the whole repo especially when you want to update also the main web page)
We leave this as the last step, once the artifacts have had time to sync up on the mirrors. Target it to: firstname.lastname@example.org, email@example.com and firstname.lastname@example.org, samples are available at Sample announcements page