[
https://jira.codehaus.org/browse/MRELEASE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-712.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Either tag option is ignored in branch goal or documentation is incomplete
> --------------------------------------------------------------------------
>
> Key: MRELEASE-712
> URL: https://jira.codehaus.org/browse/MRELEASE-712
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.2.1
> Reporter: Laird Nelson
>
> The plugin documentation for the branch goal [specifies a "tag"
> option|http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html#tag].
> It is not clear what this tag option is for.
> If you supply it during a branch operation, it appears to be ignored.
> I attempted in this command line to create a branch named foobar-0.5.X from a
> tag named foobar-0.5. Instead the branch was created from the trunk:
> {code}
> mvn release:branch -DbranchName=foobar-0.5.X -DupdateBranchVersions=true
> -DupdateWorkingCopyVersions=false -Dtag=foobar-0.5
> {code}
> The output included this:
> {code}
> [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
> {code}
> Note the copy from the trunk to the new branch. I was expecting the copy to
> be from {{^/tags/foobar-0.5}} to the new branch.
> Perhaps this is not what the tag option is for in the branch goal. If so,
> then the documentation for the tag option needs to be clarified.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
