[jira] Commented: (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT

["Geoffrey De Smet (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274900#comment-274900 ] 

Geoffrey De Smet commented on MRELEASE-699:
-------------------------------------------

I patched this, please pull my changes:
  https://github.com/apache/maven-release/pull/2

This fix also fixes the fact that RewritePomVersionsPhase.getOriginalVersionMap() was inaccurate (although that did not seem to have any bad effect).

> 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
>
> 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