title: Branch through maven from subversion tag with correct developerConnection
body: <p>I am trying to create a branch from a tag with maven but the <em>developerConnection</em> property is not updated. How do I do this through maven or editing the <em>pom.xml</em> file manually?</p>
  
  <p>We use subversion for scm and maven for build/release. I want to create a branch from the latest tag (release). We will use the branch for maintenance of the code, including bug fixes, and continue developing on the trunk. (I know that discussion of developing on trunk versus on branch is involved, and I don't want to open that up.)</p>
  
  <p>When I use release:branch to create the branch, the developerConnection property refers to the tag that I checked out of to create my working copy. I want it to point to the branch.</p>
  
  <ol>
  <li>I checked out the latest tag. (<em>foo-80.0.8</em>)</li>
  <li><p>From the command line in the working copy directory of that tag, I ran:</p>
  
  <pre><code>mvn release:branch -DbranchName=foo-80.0.8.1.x -DupdateWorkingCopyVersions=false
  </code></pre>
  
  <p>(The <em>.1.x</em> refers to the <em>1</em> st branch with <em>x</em> as a placeholder indicator for branch version.)</p></li>
  </ol>
  
  <p>In the resulting <em>pom.xml</em> in the branch on the repository, the <em>developerConnection</em> property was set to
  <em>...Foo/tags/foo-80.0.8</em> (I omitted the beginning of the URL to prevent the automatic hyperlink.) I want it to be <em>...Foo/branches/foo-80.0.8.1.x</em></p>
  
  <p>I tried again, but this time, I edited the <em>pom.xml</em> file, and changed <em>developerConnection</em> to <em>...Foo/branches/foo-80.0.8.1.x</em>. After running <code>mvn release:branch ...</code>, <em>developerConnection</em> in the <em>pom.xml</em> file still pointed to the tag.</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>I took @twomey1's suggestion. (Thanks!) Now <em>developerConnection</em> points to <code>...\tags\foo-80.0.8.1.x</code> which is not the original tag (<em>good</em>), but that tag doesn't exist (<em>bad</em>). I checked out a fresh copy of the new branch, modified <em>pom.xml</em> to point to the branch, and committed the change. When I tried <code>mvn release:prepare</code> I got this error message:</p>
  
  <pre><code>[ERROR] Failed to execute goal 
  org.apache.maven.plugins:maven-release-plugin:2.0-beta-7:prepare (default-cli) on
  project foo: You don't have a SNAPSHOT project in the reactor projects list.
  </code></pre>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>@twomey1's comment about SNAPSHOT helped. Using -DupdateVersionsToSnapshot on the command line, I got release:prepare to go forward but there still seems to be confusion with tags and branches. Again, my workflow:</p>
  
  <ol>
  <li>Run <code>svn checkout https:.../tags/foo-80.0.8</code>.</li>
  <li>Run <code>mvn -DupdateVersionsToSnapshot=true -DupdateBranchVersions=true 
  -DupdateWorkingCopyVersions=false -DbranchName=foo-80.0.8.1 release:branch</code> from the working copy of the <strong>tag</strong> that was just checked out.</li>
  <li>Run <code>svn checkout https:.../branches/foo-80.0.8.1</code> from the parent directory of the working copy.</li>
  <li>Run <code>mvn release:prepare</code> from the working copy of the <strong>branch</strong> that was just checked out.</li>
  </ol>
  
  <p>Then I get a svn error passed from maven that tag <em>foo-80.0.8.1</em> already exists. I want to create a release from the branch which should not conflict. The <em>developerConnection</em> property still points to <em>...\tags\foo-80.0.8.1</em> which doesn't exist.</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>I repeated with this difference, I added .1 to the end of the release version, the SCM release tag, and the portion of the development version before SNAPSHOT. This seems to work. I did this during <code>mvn release:prepare</code>.</p>