[
https://jira.codehaus.org/browse/MVERSIONS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294049#comment-294049
]
Daniel Johnson commented on MVERSIONS-131:
------------------------------------------
This has been a long standing problem for me as well. Has anyone been able to
find a work-around? It does not make sense to me why this only works when the
children specify the aggregator/reactor as the parent POM. Curious if it is a
limitation, or a missed corner case in the code.
> versions:set is not propagated to submodules if they don't inherit aggregator
> pom
> ---------------------------------------------------------------------------------
>
> Key: MVERSIONS-131
> URL: https://jira.codehaus.org/browse/MVERSIONS-131
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.1, 1.2
> Environment: Maven 2.2.1
> Reporter: Frédéric Camblor
> Attachments: versions-set-on-modules-problem.zip
>
>
> If we have a project A with modules B & C where :
> - B inherit from A
> - C DOESN'T inherit from A
> When we execute the following command line :
> mvn org.codehaus.mojo:versions-maven-plugin:1.2:set -DnewVersion=0.1
> Only A & B are updated.
> The fact that C doesn't inherit from A (whereas C is a module of A) doesn't
> make it updated.
--
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
