|Apache Struts 2 Documentation > Home > Guides > Contributors Guide > Creating and Signing a Distribution > Creating and Signing a Struts 2.3.x Distribution > Building Struts 2 - Normal release|
|Before starting release process make sure that the Docs were exported to https://cwiki.apache.org/WW/! Check the Version Notes page!|
Edit the top pom.xml file and replace 2.x the url below with major.minor.x part of version number that's going to be released (eg. version is 2.3.10 -> 2.3.x) and rename development folder to release.
commit the change
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 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]
|For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run:|
svn up -r head
mvn release:prepare -Dresume
|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.|
This step will (more information):
This step will (more information):
After this step the artifacts will be hosted by Nexus
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 /www/people.apache.org/builds/struts/$VERSION dir.
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 that move the assemblies directory to the builds destination with
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.
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:
If a new DTD was defined, add it to https://svn.apache.org/repos/asf/struts/site/trunk/pom.xml, in get-dtds execution section.
|The default setup on people.apache.org will leave the files and directories only changeable by the user who creates them. The last two steps will allow future releases to go smoothly.|
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:
where x is the previous version to remove (or one more previous to keep current and one version back).
Wait 24 hours before proceeding.
If the release will fix a - hopefully yet undisclosed - security issue, it's now time to update the Security Bulletins page and add a new announcement. For a template, just check former announcements
|The below is not true any more - please wait for update!|
Edit /www/struts.apache.org/$VERSION/archetype-catalog.xml and update the version of artifacts
It takes a few hours for the site changes to go live
Revert back the site target to 2.x and commit the change
Make public available all the pages that could leak confidential information about the vulnerability. Wait or manually export the space in Confluence. Build snapshot locally and copy assembly/target/assembly/out/struts2-#.#.#-SNAPSHOT-docs.zip to people.apache.org and update /www/struts.apache.org/2.x/docs
After updating the site, be sure that the permissions are set to group writeable ($ chmod -R g+w .)
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 and email@example.com, samples are available at Sample announcements page