[ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904069#comment-15904069 ]
Henning Schmiedehausen commented on MRELEASE-979: ------------------------------------------------- I would love to get this resolved to mutual satisfaction where we can both accomplish our goals, having only a single policy and being able to influence the naming policy when running release:branch. Is there any update on the "the real issue must be somewhere else in the code"? > 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)