[
https://issues.apache.org/jira/browse/MNG-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950252#comment-14950252
]
Hervé Boutemy edited comment on MNG-5763 at 10/10/15 8:54 AM:
--------------------------------------------------------------
This also happens with $\{project.version}. When you import a pom in a parent
with <version>$\{project.version}</version>, the version of the child-pom is
used:
A (1.0) imports B ($\{project.version}, expected 1.0)
C (2.0) extends A, now imports B (2.0).
was (Author: papegaaij):
This also happens with ${project.version}. When you import a pom in a parent
with <version>${project.version}</version>, the version of the child-pom is
used:
A (1.0) imports B (${project.version}, expected 1.0)
C (2.0) extends A, now imports B (2.0).
> Incorrect resolution of ${project.groupId} for POM imports with different
> groupIds
> ----------------------------------------------------------------------------------
>
> Key: MNG-5763
> URL: https://issues.apache.org/jira/browse/MNG-5763
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build, Dependencies
> Affects Versions: 3.1.1
> Environment: Apache Maven 3.1.1
> (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 17:22:22+0200)
> Java version: 1.7.0_67, vendor: Oracle Corporation
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Daniel Strassenburg
> Attachments: myproject.zip
>
>
> In the attached project find a sample which causes Maven to fail when
> resolving POM imports. The property {{$\{project.groupId\}}} is resolved
> incorrectly when
> # the imported modules have a different groupId
> # the imported POMs come from a submodule where one submodule containing a
> BOM POM has another groupId
> The groupIds of all other POM imports are changed to the groupId of the third
> BOM.
> Console output:
> {code}
> $ mvn install
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> com.mycompany.myproject.submodule:other-extension:1.0-SNAPSHOT
> (C:\dev\myproject\other-extension\pom.xml) has 2 errors
> [ERROR] Non-resolvable import POM: Failure to find
> com.mycompany.myproject.submodule:bom-1:pom:1.0-SNAPSHOT in
> http://repository-build.coremedia.com/nexus/content/repositories/snapshots.licenses/
> was cached in the local repository, resolution will not be reattempted until
> the update interval of coremedia.internal.licenses has elapsed or updates are
> forced @ com.mycompany.myproject:myroot:1.0-SNAPSHOT,
> C:\dev\myproject\pom.xml, line 19, column 19 -> [Help 2]
> [ERROR] Non-resolvable import POM: Failure to find
> com.mycompany.myproject.submodule:bom-2:pom:1.0-SNAPSHOT in
> http://repository-build.coremedia.com/nexus/content/repositories/snapshots.licenses/
> was cached in the local repository, resolution will not be reattempted until
> the update interval of coremedia.internal.licenses has elapsed or updates are
> forced @ com.mycompany.myproject:myroot:1.0-SNAPSHOT,
> C:\dev\myproject\pom.xml, line 26, column 19 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
