To keep this list current, it is strongly recommended that release managers refer to and follow this list each time a distribution is created. If any of the steps need to be amended, then please update the list.
svn co https://svn.apache.org/repos/asf/struts/maven/trunk/struts-annotations struts-annotations
mvn -Prelease release:prepare -Dusername=yourSvnUsername -Dpassword=yourSvnPassword
Accept the suggested tag name
![]() |
For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run: |
mvn release:perform
A sample template at the bottoms of the page (and DO wait for the 72 hours period)
ssh people.apache.org cp -R /www/people.apache.org/builds/struts/struts-annotations-$VERSION/m2-staging-repository/org/apache/struts/struts-annotations/ /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/struts-annotations/
svn co https://svn.apache.org/repos/asf/struts/struts2/trunk STRUTS_#_#_#
Tag the release by using the "release:prepare" goal of Maven:
mvn -Prelease release:prepare -Dusername=yourSvnUsername -Dpassword=yourSvnPassword -DautoVersionSubmodules=true
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_1_[PATCH_VERSION]
![]() |
For some reason, when using svn client 1.5, the release plugin might fail to tag the release, if it fails, run: |
This step will (more information):
mvn release:perform
This step will (more information):
After this step the artifacts will be under people.apache.org:/www/people.apache.org/builds/struts/$VERSION/m2-staging-repository/
If you need to run perform again, (or in a different box), do:
svn co http://svn.apache.org/repos/asf/struts/struts2/tags/$VERSION cd $VERSION mvn deploy site-deploy -P release --no-plugin-updates -DperformRelease=true
ssh people.apache.org cd /www/people.apache.org/builds/struts/$VERSION find m2-staging-repository -name "*.zip*" -exec cp {} . \; #remove 'struts-assembly' from the file names for src in $('ls');do trg=$(echo $src | sed -e "s/struts2-assembly/struts/");mv -v $src $trg; done #remove assembly dir rm -rdf m2-staging-repository/org/apache/struts/struts2-assembly/ #remove signature checksums rm *.asc.md5 *.asc.sha1
Post a release/quality vote to the dev list (and only the dev list).
After the vote, if the distribution is being mirrored (there was a favorable release vote) copy the Sources and Binaries:
ssh people.apache.org cd /www/people.apache.org/builds/struts/$VERSION cp struts-$VERSION-src.zip* /www/www.apache.org/dist/struts/source cp struts-$VERSION-docs.zip* /www/www.apache.org/dist/struts/documentation cp *all.zip* *apps.zip* *lib-jdk14.zip* *lib.zip* struts2-blank-*.war* /www/www.apache.org/dist/struts/binaries
Copy the Maven artifacts
cp -R /www/people.apache.org/builds/struts/$VERSION/m2-staging-repository/org/apache/struts/ /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/struts/
Wait 24 hours before proceeding.
svn co https://svn.apache.org/repos/asf/struts/site/ struts-site
mvn site-deploy
You must review the readme under m2-ibiblio-rsync for additional notes and caveats
After updating the site, be sure that the permissions are set to group writeable ($ chmod -R g+w .)
mkdir ~/.ssh chmod 700 ~/.ssh ssh-keygen -q -f ~/.ssh/id_rsa -t rsa #Enter a passphrase chmod go-rwx ~/.ssh/* #copy the public key to people.apache.org scp ~/.ssh/id_rsa.pub people.apache.org: # next, setup the public key on server ssh people.apache.org mkdir ~/.ssh chmod 700 ~/.ssh cat ~/id_rsa.pub >> ~/.ssh/authorized_keys chmod 600 ~/.ssh/authorized_keys rm ~/id_rsa.pub
svn co https://svn.apache.org/repos/asf/struts/maven/trunk/build struts-maven-build cd struts-maven-build (gpg --fingerprint --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS scp KEYS people.apache.org:/www/www.apache.org/dist/struts svn commit KEYS -m "Add public key"
Create a settings.xml under ~/.m2
<settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <servers> <server> <id>apache.snapshots</id> <username>$USERID</username> <privateKey>$PATH_TO_PRIVATE_KEY</privateKey> <passphrase>$PASSPHRASE</passphrase> <directoryPermissions>775</directoryPermissions> <filePermissions>644</filePermissions> </server> <server> <id>struts-staging</id> <username>$USERID</username> <privateKey>$PATH_TO_PRIVATE_KEY</privateKey> <passphrase>$PASSPHRASE</passphrase> </server> <server> <id>apache-site</id> <username>$USERID</username> <privateKey>$PATH_TO_PRIVATE_KEY</privateKey> <passphrase>$PASSPHRASE</passphrase> </server> </servers> <profiles> <profile> <id>cargo-config</id> <properties> <cargo.tomcat5x.home>$CATALINA_HOME</cargo.tomcat5x.home> </properties> </profile> <profile> <id>release</id> <properties> <gpg.passphrase>$PASSPHRASE</gpg.passphrase> </properties> </profile> </profiles> <activeProfiles> <activeProfile>cargo-config</activeProfile> </activeProfiles> </settings>
To complete a full build and all the tests, it may be neccesary to increase the amount of memory available to Maven. The simplest thing is to set an environment variable.
If a tagged build needs to be retagged, be sure to delete the old tag first.
svn delete https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_# -m "WW-### Removing first try at 2.#.#."
If the commit was fine, but the log was wrong, updating the log entry is easy. For example,
> svn propset --revprop -r 504523 svn:log "WW-1715 Branch for 2.0.x at Struts 2.0.6-SNAPSHOT r504196"
> property 'svn:log' set on repository revision 504523
See svn help propset for more.
The Struts Annotations 1.0.x test build is now available as a Maven artifact. It is a dependency of Struts 2.x.y. If you have had a chance to review the test build, please respond with a vote on its quality: [ ] Leave at test build [ ] Alpha [ ] Beta [ ] General Availability (GA) Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s. The vote will remain open for at least 72 hours, longer upon request.
Test builds are only announced to the dev list. Announcements to the user list can only be made pursuant to a release vote with the consent of the PMC.
The test build of Struts 2.0.3 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Struts 2.0.3 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote is called for this build. Release notes: * [LINK] Distribution: * [http://people.apache.org/builds/struts/#.#.#/] Maven 2 staging repository: * [http://people.apache.org/builds/struts/#.#.#/m2-staging-repository/] We appreciate the time and effort everyone has put toward contributing code and documentation, posting to the mailing lists, and logging issues.
The Struts #.#.# test build is now available. Release notes: * [http://struts.apache.org/2.x/docs/version-notes-###.html] Distribution: * [http://people.apache.org/builds/struts/#.#.#/] Maven 2 staging repository: * [http://people.apache.org/builds/struts/#.#.#/m2-staging-repository/] Once you have had a chance to review the test build, please respond with a vote on its quality: [ ] Leave at test build [ ] Alpha [ ] Beta [ ] General Availability (GA) Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s. The vote will remain open for at least 72 hours, longer upon request. A vote can be amended at any time to upgrade or downgrade the quality of the release based on future experience. If an initial vote designates the build as "Beta", the release will be submitted for mirroring and announced to the user list. Once released as a public beta, subsequent quality votes on a build may be held on the user list. As always, the act of voting carries certain obligations. A binding vote not only states an opinion, but means that the voter is agreeing to help do the work
The Apache Struts group is pleased to announce that Struts 2.0.6 is available as a "#####" release. \[\[The Beta designation indicates that we believe the distribution needs wider testing before being upgraded to a "General Availability" release. Your input is essential.\] The GA designation is our highest quality grade. \] [http://struts.apache.org/download.cgi#struts###] The release is also available from the central Maven repository under Group ID "org.apache.struts". The #.#.x series of the Apache Struts framework has a minimum requirement of the following specification versions: * Java Servlet #.# and JavaServer Pages (JSP) #.# * Java 2 Standard Platform Edition (J2SE) #.# The release notes are available online at: * [http://struts.apache.org/2.x/docs/release-notes-###.html] Should any issues arise with your use of any version of the Struts framework, please post your comments to the user list, and, if appropriate, file a ticket with JIRA. - The Apache Struts group.
The Struts #.#.#.1 test build is now available. Release notes: * [http://struts.apache.org/2.x/docs/release-notes-####.html] Distribution: * [http://people.apache.org/builds/struts/#.#.#.1/] Maven 2 staging repository: * [http://people.apache.org/builds/struts/#.#.#.1/m2-staging-repository/] Once you have had a chance to review the test build, please respond with a vote on its quality: [ ] Leave at test build [ ] Alpha [ ] Beta [ ] General Availability (GA) Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s. This is a "fast-track" release vote. If we have a positive vote after 24 hours (at least three binding +1s and more +1s than -1s), the release may be submitted for mirroring and announced to the usual channels. The website download link will include the mirroring timestamp parameter [1], which limits the selection of mirrors to those that have been refreshed since the indicated time and date. (After 24 hours, we \*must\* remove the timestamp parameter from the website link, to avoid unnecessary server load.) In the case of a fast-track release, the email announcement will not link directly to <download.cgi>, but to <downloads.html>, so that we can control use of the timestamp parameter. [1] <[http://apache.org/dev/mirrors.html#use|http://apache.org/dev/mirrors.html#use]>