[
https://issues.apache.org/jira/browse/MNG-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752666#comment-15752666
]
Michael Osipov commented on MNG-5736:
-------------------------------------
What is the realworld example for this? It looks like a broken setup for me.
> ProjectSorter invalid duplication checking
> ------------------------------------------
>
> Key: MNG-5736
> URL: https://issues.apache.org/jira/browse/MNG-5736
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.2.3
> Environment: n/a
> Reporter: John Patrick
> Attachments: build-patched.log, build.log, exact-same-module.zip,
> maven-core.patch.ProjectSorter.patch
>
>
> One pom has two modules, both modules link to the same third module.
> ProjectSorter detects this as a DuplicateProjectException, but in fact if you
> check getFile() for both projects they are in fact the exact same underlying
> pom.xml.
> So I've provided a patch to ProjectSorter which check and skips the
> conflicting project, prior to throwing DuplicateProjectException.
> Not sure if I should be fixing ProjectSorter or if the bug needs to be fixed
> earlier...
> Testcase, execute the parent pom, with maven-core and it fails, then build
> maven-core with the supplied patch and rebuild the parent pom.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
