[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898253#comment-15898253
]
Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------
So you are saying that it is intentional that there is no code path to move the
value of defaultTag to tag if it is a branch operation and you do not want to
change this?
Reality is that there is one naming policy for tags today, the one that uses a
default tag name and/or the scmTagName formatter unless a tag is presented and
there is another (no default, fail if no tag has been presented) for a branch.
Until you can reconcile this, it is impossible for you to accomplish your goal.
These two policies are distinguished by the branchOperation flag.
> Support NamingPolicies to manage Branch and Tag names
> -----------------------------------------------------
>
> Key: MRELEASE-979
> URL: https://issues.apache.org/jira/browse/MRELEASE-979
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: branch, prepare, update-versions
> Affects Versions: 2.5.3
> Reporter: Henning Schmiedehausen
> Fix For: 3.0.0
>
>
> The newly introduced VersionPolicy facility allows managing the development
> and release versions of projects when releasing, branching and updating
> versions.
> Most organizations will also have a policy around how branches and tags are
> named (which often have to match specific versioning patterns). The current
> VersionPolicy implementations do not allow this but it should be possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
