[
https://jira.codehaus.org/browse/MVERSIONS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292025#comment-292025
]
Chris Beach commented on MVERSIONS-115:
---------------------------------------
I'm suffering this problem too.
When versioning project A, which aggregates two parent-versioned children
(projects B and C) that inter-depend, the dependencies ARE properly updated in
B and C. No problems there.
However, when you place project A in an aggregator and run versions:set there,
dependencies in B and C aren't set.
I imagine the root cause relates to the recursion (or lack of it) inside the
mojo. Maybe the logic treats the project within which mvn is executed as a
special case (hence why the first example works).
I'd like to have a stab at fixing this and would appreciate if anyone familiar
with the code could give me their insight on this (i.e. do you already know
what the problem is?)
> Missing version update inside dependency
> ----------------------------------------
>
> Key: MVERSIONS-115
> URL: https://jira.codehaus.org/browse/MVERSIONS-115
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: maven3-beta-1
> Reporter: Marcus Holl
> Fix For: Backlog
>
> Attachments: missingversionupdate.zip
>
>
> The scenario is:
> 1.) Parent project which defines a version
> 2.) Child project that does not define an explicit version (version is
> inherited from the parent)
> 3.) Another project that holds a reference to the child project mentioned
> before in the dependency section. Inside that dependency we have to specify
> the version of the project that is referenced. Since the version of that
> project is inherited from the parent project that version is the version of
> the parent project.
> 4.) An aggregator project that collects the projects 1.) to 3.).
> Now we change the version of the parent project.
> The expected result is: The version inside the dependency definition inside
> project 3.) is updated with the new version that was applied to the parent.
> The result is: The version inside the dependency definition inside project
> 3.) is not updated with the new version that was applied to the parent.
> The call that was invoked inside the aggregator project was: mvn
> org.codehaus.mojo:versions-maven-plugin:1.2:set -DnewVersion=1.0.9-SNAPSHOT
> -DgroupId=dependencysimple -DartifactId=parent
> Attached there is a zip file (missingversionupdate.zip) that outlines that
> behaviour:
> - Inside /initial_state we have the status before any version change.
> - Inside /expected we have that expected result
> - Inside /result we have the output of the call mentioned above.
> Best regards,
> Marcus
--
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
