maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (MNG-168) dependency management for scope did not work fully
Date Tue, 15 Mar 2005 22:45:31 GMT
     [ ]
Brett Porter closed MNG-168:

    Resolution: Won't Fix

the intended behaviour of dependencyManagement is to propogate down the inheritence tree,
not up. The corect handling is to override the dependency in the parent by declaring it again
with compile scope.

> dependency management for scope did not work fully
> --------------------------------------------------
>          Key: MNG-168
>          URL:
>      Project: m2
>         Type: Bug
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>      Fix For: 1.0-alpha-1

> I had a junit dependency in the parent POM that had scope of "test". The child project
(wagon-provider-test) used dependencymanagement to assign the scope to compile, but it didn't

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message