Geoffrey De Smet created MVERSIONS-171:
------------------------------------------
Summary: Instead of always using the latest version, allow to
specify the version for versions:update-parent
Key: MVERSIONS-171
URL: https://jira.codehaus.org/browse/MVERSIONS-171
Project: Maven 2.x Versions Plugin
Issue Type: New Feature
Reporter: Geoffrey De Smet
We can't use the maven-release-plugin for various reasons, but we still like to
use mvn commands to change the version of all the modules in our multiprojects
(we have several multiprojects, in each it's won repository, which share the
same release version.
https://github.com/droolsjbpm
We first release droolsjbpm-build-bootstrap (contains the parent pom)
and then release the drools multiproject, the guvnor multiproject, ...
So we started to use the versions plugin to do that, which works fine as long
as we're releasing master, for example 5.4.0.Beta1.
However, if we're releasing a hotfix, for example 5.2.1, and we try to use the
versions plugin to switch the parent of the drools multiproject from
5.2.1-SNAPSHOT to 5.2.1.Final, it always switches it to 5.4.0.Beta1 (the
latest, highest release).
It would be very handy if we can set a version instead of letting it be
dynamically calculated.
Related to MVERSIONS-161.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
