...
The snapshot will be immediately available in the public Sonatype repository: http://oss.sonatype.org/content/groups/public
Official Releases
Update KEYS
Make sure the KEYS file at the root of the source tree has your up to date public code signing key and signatures listed. If you don't yet have a code signing key, see Creating a Code Signing Key. When you are ready, append your key with the following command:
- (gpg --list-sigs YourKeyID && gpg -a --export YourKeyID) >> KEYS
Do a Dry Run
This step is not required, but performs a useful sanity check without committing any changes. From a clean, up-to-date copy of trunk, run the following command:
- mvn release:prepare -DdryRun=true
Tag and increment the project version
This step will set the version declared in the project's pom.xml files, commit the changes to trunk, tag the release, and finally, check in another trunk change that increments the next development version (e.g. x.y-SNAPSHOT) in the pom.xml files.
- mvn release:prepare -Dresume=false -Dusername=YourSVNUsername -Dpassword=YourSVNPassword
Note: This may fail to compile part way through the process, complaining that an internal project dependency is not met. If this occurs, don't worry. Just run the following:
- mvn install
- mvn release:prepare -Dusername=YourSVNUsername -Dpassword=YourSVNPassword
Release to Staging
- Check out the tagged release from subversion and "mvn install" it.
- Change back to trunk
- mvn release:perform -Darguments="-Dgpg.keyname=YourKeyID -Dgpg.passphrase=YourKeyPassword"
This will push all release artifacts to the staging repository.