Preparing a release goes through the following release phases:
To prepare a release execute this command:
Note: If an error occurs, or the process is cancelled, then running this command again will pick up from where the last one left off.
If you wish to start again, use:
mvn release:prepare -Dresume=false
Alternatively, you can use:
mvn release:clean release:prepare
Note: If any changes have been made to your source files they might need to be reverted before you restart the prepare process. You can use release:rollback to make the plugin do it for you.
You will be prompted for the version number for each module of the project. If you prefer that every module gets the same version as the parent POM, you can set the option autoVersionSubmodules to true. Now you will be asked only once for the release version and the next development version.
It is possible to generate a release-pom.xml file for each project that contains the fully resolved project used at release time as a record for later. As of the 2.0 release, this requires calling an alternate goal:
This goal is equivalent to the release:prepare goal, except that it requires a previous build of the project to exist to properly populate the release-pom.xml files.