[
http://jira.codehaus.org/browse/MNG-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214407#action_214407
]
Brett Porter commented on MNG-3565:
-----------------------------------
I'm not the one that closed it, but my reasoning would be that this is
potentially confusing - if you happened to remove a module from the top of the
build it might still get built.
There should be no need for this feature with the reactor options presented in
Maven 2.1.0+. From the top level you would run:
{code}
mvn -pl my-teams-modules -am clean install
{code}
This would build everything under that tree, and everything that they depended
on (like common modules). If you also want to check your changes don't affect
anyone else, you could build with:
{code}
mvn -pl my-teams-modules -amd clean install
{code}
That builds any projects in the reactor that depend on the projects previously
built.
> Maven shouldn't error if a module appears twice in the reactor
> --------------------------------------------------------------
>
> Key: MNG-3565
> URL: http://jira.codehaus.org/browse/MNG-3565
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 2.0.9
> Reporter: Ittay Dror
> Attachments: MNG-3565-test-case.zip, multiproject-2.patch,
> multiproject.patch
>
>
> parent
> \-----child1
> \-----child2
> \-- many more modules...
> parent contains child1 and child2 modules
> child1/pom.xm contains '<module>../child2</module>'
> now if i cd into child1 and build, child2 is built before it. good. but if i
> run from the top directory i get:
> Project '..:child2' is duplicated in the reactor
> Note: the reason not to always run from top is that there are many modules,
> which are not interrelated, so developer shouldn't wait while another set of
> modules (maintained by another build) is built (even if nothing gets done,
> it still takes time).
> Why not just remove duplicates before sorting?
--
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
