title: Maven release: next development version in batch mode
body: <p>I have configured a Jenkins job to release my maven project automatically. This is done by using the following: <code>mvn --batch-mode clean release:prepare release:perform</code>
  In batch mode the release version and the development version will be determined automatically. This is exactly what I want.</p>
  
  <p>The problem is that I want to increase the 2nd number of the version instead of the 3rd one. So when I release version 1.2.0, the next development version must be 1.3.0-SNAPSHOT. Not 1.2.1-SNAPSHOT.
  Adding a commandline parameter is not an option, because that forces me to constantly edit the build job. </p>
  
  <p>Any suggestions on how to change the algorithm used to determine the next development version?</p>