On Fri, Oct 7, 2011 at 1:24 PM, Laird Nelson <[email protected]> wrote:
> My best guess was that maybe it was the tag from which a branch should be > created? I.e. in Subversion: svn copy ^/tags/the-tag-name-goes-here > ^/branches/the-branch-name-goes-here > Well, I tried this, and then diffed the resulting branch and the tag from which I attempted to create it. They should have been nearly identical (but for pom.xml version upgrades and some scm tweaking). They were not. It appeared that the tag option was simply ignored. My command line looked like this: mvn release:branch -DbranchName=foobar-0.5.X -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -Dtag=foobar-0.5 The output I saw included this: INFO] Executing: /bin/sh -c cd /Users/ljnelson/Projects/foobar && svn --non-interactive copy --file /var/folders/BT/BT0U2CqlGHuq-S5z-Xo+6E+++TI/-Tmp-/maven-scm-1493371414.commit --revision 964 http://blargh.com/svnrepos/foobar/trunk/foobar http://blargh.com/svnrepos/foobar/branches/foobar-0.5.X Note the copy from trunk to the branch. Oops. So now a larger question: what is the proper way to use the release:branch goal? I understand the -DupdateWorkingCopyVersions=false and -DupdateBranchVersions=true settings, and I've read http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html. But unless I am missing something this does not actually show you how to create a branch from a tag. Clearly my use of the "tag" option was incorrect. It looks like perhaps you have to check out a working copy anchored to the tag and perform the release from there? Any help is appreciated. Best, Laird -- http://about.me/lairdnelson
