[
http://jira.codehaus.org/browse/MNG-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229527#action_229527
]
Prashant Bhate commented on MNG-3565:
--------------------------------------
This command would still throw {{Project 'xxx' is duplicated in the reactor}}
exception if we try to build reactor project with decoupled module project like
{code}
super_parent # this does not define parent1 and parent2 as modules
parent1
module1
parent2
module2
{code}
this would still fail if one tries to build it from super_parent with command
"mvn -r" .
so why this issue is closed without any explanation !?
> 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
