[
https://jira.codehaus.org/browse/MVERSIONS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277967#comment-277967
]
Geoffrey De Smet commented on MVERSIONS-161:
--------------------------------------------
Update-child-modules doesn't work, because I have this setup:
{code}
repo droolsjbpm-build-bootstrap:
droolsjbpm-parent/pom.xml (with <modules> empty!)
repo drools
drools/pom.xml extends from droolsjbpm-parent (<modules> not empty)
drools/drools-core/pom.xml extends from drools
drools/drools-compiler/pom.xml extends from drools
...
repo drools-planner
drools-planner/pom.xml extends from droolsjbpm-parent (<modules> not empty)
drools-planner/drools-planner-core/pom.xml extends from drools-planner
...
...
{code}
The problem is changing the parent version of drools/pom.xml and
drools-planner/pom.xml (and 5 others) with an update-version.sh script.
> The goal's versions:update-parent's parameter parentVersion is ignored (and
> the latest version is taken)
> --------------------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-161
> URL: https://jira.codehaus.org/browse/MVERSIONS-161
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Reporter: Geoffrey De Smet
>
> I did
> {code}
> mvn -Dfull versions:update-parent -N -DparentVersion=5.3.0.CR1
> {code}
> Yet, it set the parentVersion to "5.3.0.Beta1" (= the latest stable version)
> instead of "5.3.0.CR1".
> Note that CR1 wasn't released or in my local repo yet at the time.
> If that's a problem (I hope not), it should fail-fast.
--
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
