[
https://jira.codehaus.org/browse/MRELEASE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MRELEASE-591.
-------------------------------------
Resolution: Won't Fix
Rejecting this for a number of reasons.
1. In general the principal of the maven release plugin is to only committing
to scm tested changes. So if update-versions were to commit, it should invoke a
forked build first and only commit after such a forked build completed
successfully...
2. There is a ready work-around available for people who just want to commit
the changes without such a check-build:
mvn release:update-versions scm:commit
> release:update-versions: add option to do a checkin
> ---------------------------------------------------
>
> Key: MRELEASE-591
> URL: https://jira.codehaus.org/browse/MRELEASE-591
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: Maven 2.2.1, Release-Plugin 2.0
> Reporter: Michael Wenig
> Fix For: 2.2
>
> Attachments: MRELEASE-591.patch
>
>
> Currently release:update-versions only modifies the poms locally.
> We want to run this on our hudson and expected the goal to change the version
> AND do a checkin. Unfortunately it does not...
> This is also unexpected as the documentation defines a scnCommentPrefix
> (which is not used here):
> http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html
> I would suggest a boolean-parameter 'commitChanges' which does a checkin so
> the functionality is like release:branch without creating a branch
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
