...
1 | Make sure the #One time setup steps have been performed |
|---|
2 | Update the POMs to remove "-SNAPSHOT" from the version. If you have perl installed, you can easily do it with a single command: |
|---|
| | Code Block |
|---|
perl -pi -e 's;<version>0.9.6-incubating-SNAPSHOT</version>;<version>0.9.6-incubating</version>;g' pom.xml */pom.xml
|
|
|---|
3 | Commit the POM changes |
|---|
4 | Tag the release by making a SVN copy of the head or designated revision |
|---|
| | Code Block |
|---|
svn copy -r ######
https://svn.apache.org/repos/asf/struts/struts2/trunk
https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_#_#_#
commit -m "TagUpdated r######to asversion Struts #0.#9.#6-incubating"
|
|
|---|
4 | Perform the build with documentation and install it in the local repository (this step is required because there is a bug in Maven's javadoc generation aggregated between multiple modules): | 5 | Assemble the release |
|---|
| | Code Block |
|---|
mvn clean install site -P xwork,plugins,apps,all,pre-assembly
cd assembly
mvn assembly:assembly-Pdocbook-profile,sign-release
|
|
|---|
| | Note |
|---|
This operation will also sign the release files with the gpg utility using the <username>@apache.org key. If your code signing key is under a different address, specify it by appending the following argument to the command above: -Dopenjpa.release.keyAlias=mysigningalias@somedomain.org |
|
|---|
5 | Verify the signatures: | 6 | Sign the release artifacts (in assembly/target/assembly/out) |
|---|
| | Code Block |
|---|
gpg --armormultifile --outputverify struts-#.#.#-all.zip.asc --detach-sig struts-#.#.#-all.zip
openssl md5 < struts-#.#.#-all.zip > struts-#.#.#-all.zip.mdr |
|
|---|
7 | pscp the artifacts and signatures to people.apache.org:/www/builds/struts/#.#.# |
|---|
8 | Deploy the artifacts to our Maven repository |
|---|
| | Code Block |
|---|
mvn deploy -P apps,plugins,pre-assembly |
|
| Prune any obsolete snapshots from p.a.o://www/people.apache.org/repos |
openjpa-project/target/assembly/*.asc
|
|
6 | Now actually build the javadocs and perform the deploy upload: |
|---|
| | Code Block |
|---|
mvn verify deploy -Pjavadoc-profile,sign-release
|
|
|---|
7 | Tag the view with the release number: |
|---|
| | Code Block |
|---|
svn copy -m "OpenJPA Release 0.9.6-incubating"
https://svn.apache.org/repos/asf/incubator/openjpa/trunk
https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.6-incubating
|
|
|---|
8 | Update the pom.xml files to the subsequent version with the -SNAPSHOT suffix | 9 | Update the POMs to next version number and add the "-SNAPSHOT" suffix. For example: |
|---|
| | Code Block |
|---|
perl -pi -e '"s;<version>0.9.6-incubating</version>;<version>0.9.7-incubating-SNAPSHOT</version>;g'" pom.xml */pom.xml
|
|
|---|
109 | Commit the POM changes |
|---|
11 | Deploy the new snapshot |
|---|
| | Code Block |
|---|
mvn
svn commit -N install |
| 12 | Add the next version to our issue tracker for scheduling new features and fixes m "Updated to version 0.9.7-incubating-SNAPSHOT"
|
|
|---|
One time setup
These setup steps only need to be performed on a particular machine once.
...
