[
https://jira.codehaus.org/browse/MVERSIONS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Johnson updated MVERSIONS-131:
-------------------------------------
Attachment: MVERSIONS-131_patch.txt
Here is a proposed patch. The change is to simply update all projects which had
the same version to start with as the reactor/aggregator POM. If the
reactor/aggregator POM is the <parent> the parent version is also updated as
before, but essentially it simplifies the logic by just updating all projects
with the same version instead of only those projects where the parent was the
reactor.
All unit tests still pass with this patch, but I did not check what the unit
tests are actually testing...
> 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: MVERSIONS-131_patch.txt,
> 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
