title: maven-release-plugin tag creation
body: <p>I just used maven-release-plugin to release a version, obviously :)
  The scm configuration in my parent pom is as follows:</p>
  
  
  
  <pre class="lang-xml prettyprint-override"><code>&lt;scm&gt;
      &lt;developerConnection&gt;scm:svn:http:/localhost/svn/project/trunk/project/3. Implementation/02 Source code&lt;/developerConnection&gt;
  &lt;/scm&gt;
  </code></pre>
  
  <p>As you can see, after trunk we have several more folders (RUP-style) before reaching the source code.</p>
  
  <p>A <code>mvn release:prepare</code> results in the following scm configuration:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;scm&gt;
      &lt;developerConnection&gt;scm:svn:http://localhost/svn/project/tags/project-1.0.0/02 Source code&lt;/developerConnection&gt;
  &lt;/scm&gt;
  </code></pre>
  
  <p>So, somehow, maven-release-plugin manages to replace <code>trunk/project/3. Implementation/02 Source code</code> with <code>tags/project-1.0.0/02 Source code</code>. </p>
  
  <p>Why would this not be <code>tags/project-1.0.0</code>, as I would expect? If I would run <code>mvn release:perform</code> the plugin would checkout the entire <code>3. Implementation</code> directory. </p>
  
  <p>For reference, my plugin definition is as follows:</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;plugins&gt;
      &lt;plugin&gt;
          &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
          &lt;artifactId&gt;maven-release-plugin&lt;/artifactId&gt;
      &lt;version&gt;2.5&lt;/version&gt;
          &lt;configuration&gt;
              &lt;tagBase&gt;http://localhost/svn/project/tags&lt;/tagBase&gt;
          &lt;/configuration&gt;
      &lt;/plugin&gt;
  &lt;/plugins&gt;
  </code></pre>