You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "denis dudinski (JIRA)" <ji...@codehaus.org> on 2009/04/14 12:08:52 UTC
[jira] Commented: (MNG-3565) Maven shouldn't error if a module
appears twice in the reactor
[ http://jira.codehaus.org/browse/MNG-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172880#action_172880 ]
denis dudinski commented on MNG-3565:
-------------------------------------
This problem has big influence on our project. We have around one hundred modules that participate in build. All this amount is divided into three sub modules: web application, external services application and data processing application. All three subprojects have links to some amount of common modules that are our framework. There are three big teams that want to checkout and build only their part of owerall project. And here things go right. But also it is needed to build aggregate project that consists from all three application. Because of common modules we cannot simply go to high level pom.xml and type "mvn install" and aquire package with three applications included along with some other specific build logic. Also we cannot properly collect db creation scripts for our application since our db scripts are distributed among functional modules in all three sub projects. Assembly plugin will not be started because of "Project '..:child2' is duplicated in the reactor" exc
eption.
Dependency graph:
subproject 1 ----->
| |
superparent ----> framework module--------->other framework module
| |
subproject 2------>
We cannot exclude framework modules from build.
> 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
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 2.0.9
> Reporter: Ittay Dror
> Fix For: 2.1.x
>
>
> 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