[
http://jira.codehaus.org/browse/MRELEASE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217177#action_217177
]
Maarten Billemont commented on MRELEASE-541:
--------------------------------------------
I'll add what may seem obvious but might be GIT (our SCM)-specific: You don't
need a new commit to make a new branch; you can just start a branch from any
commit.
> tries to make empty commits when version doesn't change.
> --------------------------------------------------------
>
> Key: MRELEASE-541
> URL: http://jira.codehaus.org/browse/MRELEASE-541
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0
> Reporter: Maarten Billemont
>
> We use "SNAPSHOT" as the development version, so not "X.Y-SNAPSHOT". When we
> use goals such as release:branch to create a release branch, the release
> plugin tries to create a new commit for that branch even though nothing was
> changed in code (the main branch uses SNAPSHOT as version and the maintenance
> branch uses SNAPSHOT too).
> The release plugin should check whether there are changes before attempting
> to perform a commit after updating versions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
