[
http://jira.codehaus.org/browse/MVERSIONS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pabst updated MVERSIONS-146:
---------------------------------
Attachment: MVERSIONS-145.diff
Here is the patch. It is a "git svn diff". The change can also be seen here:
https://github.com/epabst/codehaus-mojo/commit/09f2e5390597356afebba40518d17e88a4af425a
> Support updating a version property on the command-line w/o
> versions-maven-plugin configuration
> -----------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-146
> URL: http://jira.codehaus.org/browse/MVERSIONS-146
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Affects Versions: 1.2
> Environment: Maven 2 or 3
> Reporter: Eric Pabst
> Attachments: MVERSIONS-145.diff
>
>
> I'd like to update a version property to a specific value (or within a range)
> from the command-line without having to provide custom versions-maven-plugin
> configuration in the pom.xml.
> After our integration tests, we want to "promote" the versions of the
> artifacts that were successful together. We don't want it to just get the
> latest because that is too loose for our process. Something like this would
> be great:
> mvn versions:update-property -Dproperty=foo.version -DnewVersion=[2.0]
> It would update the pom.xml from:
> <foo.version>1.4</foo.version>
> to:
> <foo.version>2.0</foo.version>
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
