[
https://issues.apache.org/jira/browse/MRELEASE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-706.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Add "scmTagComment" and "scmPostTagComment" parameters
> ------------------------------------------------------
>
> Key: MRELEASE-706
> URL: https://issues.apache.org/jira/browse/MRELEASE-706
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Reporter: Jackie Noi
>
> Could you add two parameters that control what get written in the SCM comment
> when {{mvn release:prepare}} is run?
> I suggest:
> * {{scmTagComment}}: what should be written in the commit message of the tag;
> * {{scmPostTagComment}}: what should be written in commit message for the
> commit with the new version.
> For example, in my project ProjectFOO I would set {{scmTagComment}} to
> "Released ProjectFOO (v@{project.version})" and {{scmPostTagComment}} to
> "Prepare for ProjectFOO next development iteration (v@{project.version})". (I
> suppose @{project.version} will change after the tag has been put.)
> Changing commit message of already tagged commits is an uncomfortable process
> in SVN and Git, I'd love having {{mvn release:prepare}} get it right instead
> of having to fix it manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
