[
https://jira.codehaus.org/browse/MVERSIONS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277897#comment-277897
]
Paul Gier commented on MVERSIONS-161:
-------------------------------------
I think the parentVersion parameter is meant to be a range to use when the
plugin updates the parent version [1]. So by default it will look in the
repository and grab the latest, but if you only want the latest within a
specific range, then you use the parentVersion parameter. If you are using
this to update a multi-module build, you might try the update-child-modules
goal instead [2].
[1]http://mojo.codehaus.org/versions-maven-plugin/examples/update-parent.html
[2]http://mojo.codehaus.org/versions-maven-plugin/examples/update-child-modules.html
> 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
