[
http://jira.codehaus.org/browse/MRELEASE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169894#action_169894
]
Philippe Laflamme commented on MRELEASE-372:
--------------------------------------------
Our SVN structure is as follows:
trunk/
branches/
tags/
Which is standard, but for release tags and branches, we use a sub-directory
under tags and branches:
tags/releases/2.3.4
branches/releases/2.3.x
So we use tagBase to override the default tag location. This works fine for
release:prepare, but for release:branch, our branches end up under
tags/releases. Which is obviously not what we want...
Having branchBase would allow our use case.
> add branchBase optional parameter for release:branch goal
> ---------------------------------------------------------
>
> Key: MRELEASE-372
> URL: http://jira.codehaus.org/browse/MRELEASE-372
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: branch
> Affects Versions: 2.0-beta-8
> Reporter: Michael Mallete
> Attachments: MRELEASE-372-maven-release-plugin.patch
>
>
> Add a branchBase optional parameter in order to have control on where the
> branch produced by release:branch goal goes to.
> Example:
> mvn release:branch -DbranchName=branchName -DbranchBase=https://branchGoesHere
> where branch branchName goes to directory https://branchGoesHere
--
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
