[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895205#comment-15895205
]
ASF GitHub Bot commented on MRELEASE-979:
-----------------------------------------
GitHub user hgschmie opened a pull request:
https://github.com/apache/maven-release/pull/15
MRELEASE-979 - use split policies
This is a rewrite of #14 to use split policies for branching and tagging as
suggested by @rfscholte .
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hgschmie/maven-release
MRELEASE-979-split-policies
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-release/pull/15.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #15
----
commit ed33f581b5948e0880dfc61cb1fdb3c0e33ac11a
Author: Henning Schmiedehausen <henning.schmiedehau...@zuora.com>
Date: 2017-03-03T18:32:40Z
adds missing naming policy id copy opeations
commit 85c82718e0953d6fd378dcc77622b2e2ae346ae7
Author: Henning Schmiedehausen <henning.schmiedehau...@zuora.com>
Date: 2017-03-03T18:37:56Z
Adds a second policy for branch naming as compared to tag naming.
Use different configuration settings for branch and tag naming. Add a
second default policy that is used
when naming branches.
commit f7712f1fe0e16bbfb0fa39d9458c9b4f741c0273
Author: Henning Schmiedehausen <henning.schmiedehau...@zuora.com>
Date: 2017-03-03T22:51:50Z
Fixes the naming policy logic.
- Ensure that the naming policy is executed when a branch is requested
even if an scm tag name is set.
- Ensure that in non-interactive mode, the plugin does not fail
unconditionally if a branch is requested.
----
> 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)
