versions:update-parent's should take relativePath of the parent pom into
account to restrict the parentVersion
--------------------------------------------------------------------------------------------------------------
Key: MVERSIONS-162
URL: https://jira.codehaus.org/browse/MVERSIONS-162
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Reporter: Geoffrey De Smet
Priority: Minor
If I have
- droolsjbpm-parent/pom.xml with version 5.3.0.CR1, but I have not installed
that yet
- drools/pom.xml which
-- extends droolsjbpm-parent 5.3.0-SNAPSHOT
-- has the parent's relativePath set to ../droolsjbpm-parent/pom.xml
- drools-planner/pom.xml which
-- extends droolsjbpm-parent 5.3.0-SNAPSHOT
-- has the parent's relativePath set to ../droolsjbpm-parent/pom.xml
- ...
and then on drools/pom.xml or drools-planner/pom.xml, I do
mvn versions:update-parent
then it sets the parent version to 5.3.0.Beta2 (the last one in the local
repository), not 5.3.0.CR1 as it should.
Spawned from MVERSIONS-161.
--
This message is automatically generated by JIRA.
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