[ 
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840457#comment-15840457
 ] 

Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------

About "two different implementations": For custom implementations you are 
correct, there would be different implementations. For the default use case, 
using the default tag is sufficient, it makes the plugin behave the same way as 
if no policy is defined.

> 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.4#6332)

Reply via email to