[
https://issues.apache.org/jira/browse/MNG-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076295#comment-15076295
]
ASF GitHub Bot commented on MNG-5956:
-------------------------------------
Github user nhojpatrick commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168305170
I've worked on 5+ projects where they ranged from 75-150 maven projects.
Allow this configuration would have simplified and reduce build times. The
usual work around I've seen is developers creating scripts to manually navigate
to dependencies within the same multi module project structure. When you have
10-40 developers working on a project I would prefer maven to handle this so
everyone uses mvn clean install, instead of scripts being email or shared
around or random scripts littering the repo.
I've created a very basic project which demonstrates what I would like to
allow happen and current fails.
https://github.com/nhojpatrick/apache.maven.maven-core.MNG-5956
> Invalid DuplicateProjectException if physically same pom.xml
> ------------------------------------------------------------
>
> Key: MNG-5956
> URL: https://issues.apache.org/jira/browse/MNG-5956
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.x
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
> Maven home: /opt/local/share/java/maven3
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.2", arch: "x86_64", family: "mac"
> Reporter: John Patrick
> Labels: github-import, newbie, patch
>
> Several projects I've worked on have lots of modules, some to aid developers
> sub modules have been hijacked to also build other projects. Take the
> following example.
> ./pom.xml
> ./common/pom.xml
> ./sub1/pom.xml
> ./sub2/pom.xml
> If sub1 and sub2 both include <module>../common</module> then
> DuplicateProjectException is thrown. I've created a patch which before
> throwing the exception does one last check to ignore instances where the
> clash is actually the same physical pom file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
