Differences between revisions 3 and 4
Revision 3 as of 2009-03-04 18:34:57
Size: 1502
Editor: chello084113196060
Revision 4 as of 2009-09-20 23:00:49
Size: 1502
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Create an Orchestra release without using the Maven Release Plugin


  • gpg --gen-key # needed if no gpg key already created
  • create an entry for id "myfaces-staging" in ~/.m2/settings.xml
  • run "ssh-add {path-to-apache-key}" to enable authentication for later ssh-related operations

Releasing the Parent Pom

If the parent pom has updates that are needed in order for the orchestra module to be released, then do the following. Note that if the pom only has updates that affect how the site looks, then releasing the parent pom is not necessary, as we always create the site from the trunk.

svn cp maven branches/maven-1_1
update pom.xml version to next release snapshot
svn switch to branch
update pom to 1.2
mvn clean deploy -Psign-artifacts -DperformRelease -Dusername=skitching

Releasing the Core module

svn cp core branches/core-1_1
update pom version in trunk to next release snapshot

svn switch to branch
update pom to non-snapshot version

mvn clean site javadoc:jar assembly:assembly verify gpg:sign deploy -Psign-artifacts -DperformRelease=true

cd target
md5sum {assemblyname}.tar.gz > {assemblyname}.tar.gz.md5
gpg --detach-sign --armor {assemblyname}.tar.gz
md5sum {assemblyname}.zip > {assemblyname}.zip.md5
gpg --detach-sign --armor {assemblyname}.zip

tar cfz upload.tar.gz *
sftp people.apache.org
put upload.tar.gz

unpack into public_html

Post-vote tasks

  • move branches to tags

OrchestraReleaseManual (last edited 2009-09-20 23:00:49 by localhost)