[
https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoffrey De Smet updated MRELEASE-699:
--------------------------------------
Attachment: 0001-MRELEASE-699-release-update-versions-should-support-.patch
No problem :) I did:
git format-patch 124470185de7f3218380f2d7c0a384495ebb9955
and attached that file.
That's probably a git patch, not an old-school patch. If you want an old-school
patch, please inform me how I can create that from a command line or intelliJ
after the changes have already been committed.
> 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
