title: Avoid update POM versions for next development iteration with maven-release-plugin
body: <p>I'm doing my first release with <em>maven-release-plugin</em> and git. Instead of tagging I'm using the <em>release:branch</em> goal. I'm agree with the complete relase-flow process except in one point: all local dependencies are automatically updated to the next SNAPSHOT version in the development branch.</p>
  
  <p>This is my concrete situation: I'm working in a project with more than 20 maven projects. Let's say all of them are in SNAPSHOT version during development. I want to make a release with the maven plugin. After the release is done, all POM versions have been incremented and set again to SNAPSHOT. If I need to make a change in just one line of code of one project (fix a bug) and I make a new release, all projects (by default) must increment their version again when I've just changed <strong>one of them</strong>.</p>
  
  <p>In my opinion, it makes more sense to continue the development with the state of the last release (all version <strong>without</strong> SNAPSHOT). In the next development iteration, I can set manually the next SNAPSHOT version only in these projects that I have changed. In the next release, only the changed projects will be "promoted" to a new version but not all of them.</p>
  
  <p>I think this situation is not exceptional but I didn't found information how to do it (and I don't know if I'm breaking the "release" phylosophy...)</p>
  
  <p>Somedy knows how to avoid update all POMs to the next SNAPSHOT version and leave the POM files as the relase version?</p>
  
  <p>Thank you in advance!</p>