[
https://jira.codehaus.org/browse/MVERSIONS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MVERSIONS-161.
--------------------------------------
Resolution: Not A Bug
update-parent should never leave the project in a state where you cannot
initiate the lifecycle.
Therefore it can only update to a parent version that is resolvable from one
of: the current reactor; the local repo; or the current remote repos.
In your example, you are specifically using a single project reactor and the
parent version you want to update to is not in any of the three sources.
To achieve what you are trying to do, I would
cd ..
mvn versions:update-child-modules
cd -
assuming that your parent is an aggregator, otherwise just edit the one pom.xml
by hand!
> 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
