[
https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898068#comment-15898068
]
ASF GitHub Bot commented on MRELEASE-979:
-----------------------------------------
GitHub user hgschmie opened a pull request:
https://github.com/apache/maven-release/pull/17
MRELEASE-979 - fix no branch name problem
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hgschmie/maven-release
MRELEASE-979-fix-no-branchname
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-release/pull/17.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 #17
----
commit aca037bc3cfd80a42631c9aa7641a610d47e6bc2
Author: Henning Schmiedehausen <henning.schmiedehau...@zuora.com>
Date: 2017-03-06T20:34:02Z
fixes 'no branch name given' error when using a naming policy
----
> 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)
