This will move you up a version in your code. Say, for example your last released version is 1.2 (meaning the pom.xml on HEAD is on 1.3-SNAPSHOT), by default your release version will be moved to 1.3 and the version on the pom.xml on HEAD will be moved to version 1.4-SNAPSHOT.
A nice feature is that if you use the flag -dryRun=true on either of the above commands you can go through all the steps without any of the files being checked in. It gives you an opportunity to examine the changes to the pom.xml files before you go through with the commit.
To facilitate the release procedure you need to have these lines configured in your highest level pom.xml file.
<scm <connection>scm:git:email@example.com:YourRepository.git</connection <url>scm:git:firstname.lastname@example.org: com:YourRepository.git</url> </scm>
By default the code will be built and deployed to a server. Typically you will want to deploy to Maven Central or to a local Nexus server. This is done using the releaseProfiles property in the maven-release-plugin.
But this will not always be the case. If you just want to do a release of the code, to Git for example, and not deploy the code anywhere you need to override the default maven-release-plugin goal property, which by default is set to deploy and set it to install as below:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.5.1</version> <configuration> <goals>install</goals> </configuration> </plugin>