[
https://jira.codehaus.org/browse/MRELEASE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302156#comment-302156
]
Joseph Walton commented on MRELEASE-728:
----------------------------------------
You're right, the current behaviour doesn't match the original report exactly,
but I think it's correct.
By default, there is no commit in the new branch - it keeps the same version as
the original branch. The commit message in the original branch is:
{noformat}
[maven-release-plugin] prepare for next development iteration
{noformat}
Which is what you want in a branch-for-release workflow. If you use
{{updateBranchVersions}} then you end up with:
||commit||branch||commit message||
|3|master|[maven-release-plugin] prepare for next development iteration|
|2|new-branch|[maven-release-plugin] prepare branch new-branch|
|1| |[maven-release-plugin] prepare for next development iteration|
The unnecessary commit in master is due to MRELEASE-729, but I think the
messages are fine.
> The commit message for release:branch is wrong
> ----------------------------------------------
>
> Key: MRELEASE-728
> URL: https://jira.codehaus.org/browse/MRELEASE-728
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, Git
> Affects Versions: 2.2.1
> Environment: git 1.7.5.4
> Reporter: Adrien Ragot
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Using Git, when you do mvn release:branch -DbranchName=xxx,
> the commit message for master is "[maven-release-plugin] prepare release xxx".
> The right commit message should be "[maven-release-plugin] prepare branch
> xxx", like for Svn.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
