[
https://jira.codehaus.org/browse/MNG-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281996#comment-281996
]
Sarah Gerweck commented on MNG-4265:
------------------------------------
This is a really annoying issue.
> Properties in "system"-scope dependencies breaks transitive dependency
> resolution
> ---------------------------------------------------------------------------------
>
> Key: MNG-4265
> URL: https://jira.codehaus.org/browse/MNG-4265
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
> Affects Versions: 2.0.9, 2.0.10, 2.1.0-M1, 2.1.0, 2.2.0
> Reporter: Marc Wilhelm
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: maven-properties-bug.tgz
>
>
> If a used dependency (see artifact "component" in the attached example)
> contains itself a system-scope dependency (here "${JAVA_HOME}/lib/tools.jar")
> with properties, all transitive dependencies are ignored by the following
> warning:
> {code:xml}
> [WARNING] POM for 'maven.bug:component:pom:0.0.1-SNAPSHOT:compile' is invalid.
> Its dependencies (if any) will NOT be available to the current build.
> {code}
> NOTE: The transitive dependencies are handled correctly when building from a
> (reactor) project, which builds both modules, the "component" and the "app".
> But it fails when trying to build the "app" isolated as single project.
> If running the sample project against maven (2.0.4 up to) 2.0.8 it works
> fine, without problems.
> Steps to reproduce:
> - extract sample project
> - ensure environment var JAVA_HOME is set properly
> - build top level project by "mvn clean install". This should build without
> warnings
> - change into sub folder "app"
> - build module "app" via "mvn clean install". You should get the warning
> about an invalid used pom.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
