|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
Now you should be on
release/X.X.X.X branch (
git status supposed to confirm that). You must push changes to remote repo as the Release plugins will push changes to remote as well (it's already done after publishing release).
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]
Follow the link to get more information about performed operation by release plugin.
If you need to run perform again, (or in a different box), do:
Next, log in to Nexus and close staging repository.
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 firstname.lastname@example.org 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. If the release branch was published to the remote it won't be deleted locally, it must be done manually after removing branch from the remote:
This will remove the branch from the remote, now we can merge once more the release branch (when on
develop) and remove it
develop branches should be up to date with the changes introduced by the release.
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) copy the Sources and Binaries:
Remove the old files from under
/www/www.apache.org/dist/struts/ to synchronise only the latest version with peers. All the files from
/www/www.apache.org/dist/ 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-production, then commit changes. Next step is to update exported wiki pages. With current approach the pages are kept in
X is the current branch (ie. 2.3.x, 2.2.x and so on). Simply remove the whole content from under
/docs and update it with docs from assembly (you can download one from Maven repository or copy generated during release process which supposes to be in
struts/assembly/target/cwiki). And commit changes.
Checkout source of the website and export Confluence pages
Now the whole Confluence space is exported to
Checkout copy of production website
(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:
email@example.com, samples are available at Sample announcements page