[
https://jira.codehaus.org/browse/MRELEASE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315231#comment-315231
]
Darryl L. Miles commented on MRELEASE-780:
------------------------------------------
How do you mean exactly ?
You are speaking about a release that is made when a tag is created ?
* As it looks like project.scm.tag is edited to be the tag name that is
created. In which case the new pom.xml is committed (with this change) into
the tag version.
* There is also the message that appears in the SCM commit log history to help
identify the commit as being for a particular release.
There are other bugs about excess commits showing up in the main tree relating
to releases and branches. But if I understand your bug here correctly you
have used release:branch already, then did some work on the topic, then decide
to release:prepare from that branch ? So there should be at least 1 commit for
the 2 reasons cited above IMHO. Please update this ticket in respect of how
you think it should be working.
> Prevent Tag from additional commits
> ------------------------------------
>
> Key: MRELEASE-780
> URL: https://jira.codehaus.org/browse/MRELEASE-780
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.3.2
> Reporter: E
>
> If you create an release from the branch there should be no commits on the
> tag-folder.
--
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
