John Patrick created MNG-5956:
---------------------------------
Summary: 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
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)
