[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838240#comment-15838240
]
Henning Schmiedehausen commented on MRELEASE-979:
-------------------------------------------------
[~rfscholte] What is the preferred approach? I can easily refactor this to be
its own interface to implement (which makes simple implementations for both
types of policy more cumbersome because of Plexus limitations).
Ultimately, we here at Zuora want to have an internal VersionPolicy that
manages both versions and branch and tag names. Whether it is one or two
classes does not really matter to me. Right now, i can not have the tag /
branch versioning because the release plugin does not support it.
> 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)