[
http://jira.codehaus.org/browse/MRELEASE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Mallete updated MRELEASE-371:
-------------------------------------
Attachment: MRELEASE-371-maven-release-plugin.patch
Patch attached. Instead of expecting tagBase to change branching behavior, it
is more appropriate to introduce branchBase. So:
mvn release:branch -DbranchName=branchName
-DbranchBase=https://whereeveryouwanttobranchto
> tagBase not working for release:branch goal
> -------------------------------------------
>
> Key: MRELEASE-371
> URL: http://jira.codehaus.org/browse/MRELEASE-371
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Reporter: Michael Mallete
> Attachments: MRELEASE-371-maven-release-plugin.patch
>
>
> I am trying to branch to a different directory than <head>/branches. I tried:
> mvn release:branch -DupdateBranchVersions=true
> -DupdateWorkingCopyVersions=false -DautoVersionSubmodules=true
> -DtagBase=file:///someotherplace
> But still goes to <head>/branches and not to "someotherplace"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
