Page History
...
| Note | ||
|---|---|---|
| ||
These same steps are also covered in theSonatype Maven Repository Usage Guide Info | |
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
You will have to enter in your GPG passphrase (which you established when you created your Code Signing Key).
Tag and Increment 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
(Optionally, you may also include the parameters -Dusername=YourSVNUsername -Dpassword=YourSVNPassword, though I've not found these to be necessary)
You will have to enter in your GPG passphrase (which you established when you created your Code Signing Key).
| Info | ||
|---|---|---|
| ||
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:
|
| Note | ||
|---|---|---|
| ||
If backing out of this step is needed for any reason, the following will restore the subversion repository and your working copy to the state it was previously in:
|
...
Overview
Content Tools