maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] (MNG-4265) Properties in "system"-scope dependencies breaks transitive dependency resolution
Date Wed, 02 Jul 2014 13:45:20 GMT


Paul Benedict updated MNG-4265:

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Properties in "system"-scope dependencies breaks transitive dependency resolution
> ---------------------------------------------------------------------------------
>                 Key: MNG-4265
>                 URL:
>             Project: Maven
>          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
>         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
> 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 was sent by Atlassian JIRA

View raw message