[
https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277763#comment-277763
]
Brett Porter commented on MRELEASE-699:
---------------------------------------
There's several things here:
* I'm not quite sure of the motivation for update-versions in the first place -
maybe we should recommend the versions plugin instead
* regardless of the above, we need to document the differences, and fix the
misleading statement (or apply this patch)
* we still need to look at the one line change that appears to be correct but
doesn't reference a specific fix
> release:update-versions should support -DreleaseVersion too (not only
> -DdevelopmentVersion), so it also supports not suffixing the version with
> -SNAPSHOT
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-699
> URL: https://jira.codehaus.org/browse/MRELEASE-699
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Reporter: Geoffrey De Smet
> Attachments:
> 0001-MRELEASE-699-release-update-versions-should-support-.patch
>
>
> The documentation
>
> http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html
> states "The update-versions goal can use the same properties used by the
> prepare goal for specifying the versions to be used."
> That's not true, as releaseVersion is not supported:
>
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion
> This means, that if you do this:
> mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0
> that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
