[
https://issues.apache.org/jira/browse/MRELEASE-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874833#comment-15874833
]
ASF GitHub Bot commented on MRELEASE-980:
-----------------------------------------
GitHub user jodastephen opened a pull request:
https://github.com/apache/maven-release/pull/13
MRELEASE-980 Allow commit comments to be controlled
Provide the ability to override commit comments from configuration.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jodastephen/maven-release comment-control
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-release/pull/13.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 #13
----
commit 35b2a50900cfc8e8fca88a94e46985a09e538e86
Author: Stephen Colebourne <scolebou...@joda.org>
Date: 2017-02-17T12:40:56Z
Allow commit comments to be controlled
Provide the ability to override commit comments from configuration
----
> Provide the ability to control commit messages
> ----------------------------------------------
>
> Key: MRELEASE-980
> URL: https://issues.apache.org/jira/browse/MRELEASE-980
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.5.3
> Reporter: Stephen Colebourne
> Fix For: 3.0.0
>
>
> The commit messages used by maven-release-plugin are rather ugly to my eyes.
> While the comment prefix provides some control, what is really needed is to
> be able to change the whole message from xml configuration.
> I've implemented this here:
> https://github.com/jodastephen/maven-release/commit/35b2a50900cfc8e8fca88a94e46985a09e538e86
> (all rights granted to Apache - I'm still a committer at Apache Commons.
> It adds four new properties that allow the commit message to be controlled at
> various points. The commit message can be configured using `@{}` style
> inserts. There are more messages that could be controlled, but these were all
> I needed.
> Note that issue MRELEASE-706 originally requested this feature, but it was
> closed due to inactivity.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
