[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848846#comment-15848846
]
Robert Scholte commented on MRELEASE-979:
-----------------------------------------
This is getting better. However, the calculation of the name is still done
outside of the policy, that's not what I would expect. Instead the request
should at least have the artifactId and version, the result of the
DefaultNamingPolicy would be artifactId-version. And it shouldn't matter for
the policy if it is a branch or not.
> Allow VersionPolicies 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)