<server> <id>archiva-repository.releases</id> <username></username> <password></password> </server>
<profile> <id>apache-release</id> <properties> <gpg.passphrase>[GPG_PASSWORD]</gpg.passphrase> </properties> </profile>
Set your user credentials for the stage repo in the servers section of your settings.xml for archiva-repository.releases.
Execute mvn release:prepare (check that it has been properly tagged. the tag name must be.. archiva-[VERSION]).
Next, execute mvn release:perform
Download the uploaded files via wget:
ex. wget http://archiva-repository.apache.org/archiva/repository/staged-releases/org/apache/archiva/archiva-jetty/1.3/archiva-jetty-1.3-bin.tar.gz Verify the signatures: ex. gpg -v archiva-jetty-1.3-bin.zip.asc
The documentation is deployed as part of the process to the final location for review in the vote: http://archiva.apache.org/docs/1.3/. If the vote doesn't pass, the documentation will need to be removed from the server for redeployment. Commit the sources and binaries from org/apache/archiva/archiva-jetty, and org/apache/archiva/archiva to the svn distribution tree. First in dev tree: https://dist.apache.org/repos/dist/dev/archiva/ (if the vote pass they will be copied to release tree) https://dist.apache.org/repos/dist/release/archiva
svn co https://dist.apache.org/repos/dist/dev/archiva/ archiva-dev-release cd archiva-dev-release sh ./release-script-svn.sh VERSION STAGING_URL
Call for a vote in the dev list and wait for 72 hrs. for the vote results. 3 binding votes are necessary for the release to be finalized. example If the vote fails or needs to be canceled, the version number should not be re-used if the version was made available for public download. After the vote has passed, move the files from dist dev to dist release: svn mv https://dist.apache.org/repos/dist/dev/archiva/ to https://dist.apache.org/repos/dist/relase/archiva/ To sync the jars to ibiblio, execute:
NOTE: the stage plugin doesn't work with maven3 you must use maven 2.2.1
mvn stage:copy -Dsource="https://archiva-repository.apache.org/archiva/repository/archiva-releases-stage/" -Dtarget="scp://[APACHE_USERNAME]@people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" -Dversion=1.3 -DrepositoryId=apache.releases
mark the appropriate release version in JIRA as complete Update the archiva site (https://svn.apache.org/repos/asf/archiva/site/) for the versions and release notes URL and run mvn site-deploy. The 3 properties to change are at the bottom of pom.xml before generating the site. Once mirroring done (can be 24H): remove previous versions from https://dist.apache.org/repos/dist/release/archiva/
Publish the reference docs (sh ./deploySite.sh in the archiva-modules directory) from the release tag. You may have to exclude the archiva-webapp module to do this, and will require MAVEN_OPTS=-Xmx256m. You may need to use Maven 2.2.1 instead of Maven 3.x for this.
Send out an announcement of the release to: