title: Maven Release from Tagged Release Candidate or Branch
body: <p>Consider the following scenario: I have a project being developed using <code>maven</code> as build tool and <code>svn</code> or some other tool for version control.</p>
  
  <p>At some point I decide that it is "probably" ready for release and I set an <code>svn</code> tag to mark it as <code>release candidate</code></p>
  
  <pre><code>+ Trunk (0.0.1-SNAPSHOT)
  |
  +----------------------------+ Branch "release-candidate" (0.0.1-SNAPSHOT)
  |                            | (goes to QA for testing)
  + Trunk (0.0.2-SNAPSHOT)     | 
  | (development continues)    + Tag "release-0.0.1" (0.0.1)
  ....                           (deploy this revision)
  </code></pre>
  
  <p>At this point I need to update the <code>pom.xml</code> with the new development version.
  The <code>release-candidate</code> keeps the snapshot version until the QA is done with testing and declares the release ready. Only then will the actual release + deploy be performed on the tag/branch. </p>
  
  <p>Development can continue in the trunk while the release-candidate is being tested. </p>
  
  <p>Can this 2-step release scenario be realized with maven builds? Is the <code>release</code> plugin enough for this or do I need others? </p>