[
http://jira.codehaus.org/browse/MVERSIONS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seb V closed MVERSIONS-41.
--------------------------
Resolution: Duplicate
Sorry, probably a duplicate of MVERSIONS-40
> update-child-modules stops at intermediate child module with pom packaging
> --------------------------------------------------------------------------
>
> Key: MVERSIONS-41
> URL: http://jira.codehaus.org/browse/MVERSIONS-41
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-3
> Environment: $ mvn -version
> Maven version: 2.0.10
> Java version: 1.6.0_13
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Seb V
>
> We have the following POM layout :
> root (packaging: pom)
> - module 1 (packaging: jar)
> - module 2 (packaging: jar)
> - module 3 (packaging: pom)
> -- submodule 1 (packaging: jar)
> -- submodule 2 (packaging: jar)
> - module 4 (packaging: jar)
> When running mvn versions:update-child-modules, only module [1-4] are
> updated; submodule [1-2] are ignored.
> I can imagine this is by design because the parent of submodule [1-2] is
> module 3 and not root (which is the one actually being processed), but having
> to run an extra mvn versions:update-child-modules in module 3 is not very
> convenient.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
