...
- Do a dry run of the release/prepare step by executing
mvn -P apache-release release:prepare -DdryRun=true
. The dry run will not commit any changes back to Git and gives you the opportunity to verify that the release process will complete as expected. If you need to cancel, executemvn release:clean
and then reset viagit reset --hard
. - Verify that the release process completed as expected:
- The release plugin will create
pom.xml.tag
files which contain the changes that would have been committed to SVN. The only differences betweenpom.xml.tag
and its correspondingpom.xml
file should be the version number. - If other formatting changes have been made you should review the changes and then commit and push them.
- Once any failures or required updates have been committed to svn, rollback the release prepare files:
mvn release:rollback
- The release plugin will create
- Execute the release/prepare step for real this time
- You'll be prompted for the same version information and optionally your GPG
passphrase again mvn -P apache-release release:prepare
mvn -P apache-release release:perform
git push --tags
- You'll be prompted for the same version information and optionally your GPG
- Verify the staged artifacts in the Apache Nexus repository:
- Go to: https://repository.apache.org/index.html
- Enterprise > Staging
- Staging tab > Name column > curator
- Login
- Select Staging Repositories under the Build Promotion section on the left hand side
- Select the repository from the main window
- Select the content tab at the bottom of the screen and navigate Navigate through the artifact tree and double check things.
- Close the Nexus staging repo by clicking on the curator repo and clicking the "Close" button.
- IMPORTANT: Do NOT release the binaries yet
...