You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/03/08 08:16:41 UTC

[jira] Created: (MNG-168) dependency management for scope did not work fully

dependency management for scope did not work fully
--------------------------------------------------

         Key: MNG-168
         URL: http://jira.codehaus.org/browse/MNG-168
     Project: m2
        Type: Bug
    Reporter: Brett Porter


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 take.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Closed: (MNG-168) dependency management for scope did not work fully

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-168?page=history ]
     
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: http://jira.codehaus.org/browse/MNG-168
>      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 take.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (MNG-168) dependency management for scope did not work fully

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-168?page=history ]

Brett Porter updated MNG-168:
-----------------------------

    Fix Version: 1.0-alpha-1

> dependency management for scope did not work fully
> --------------------------------------------------
>
>          Key: MNG-168
>          URL: http://jira.codehaus.org/browse/MNG-168
>      Project: m2
>         Type: Bug
>     Reporter: 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 take.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (MNG-168) dependency management for scope did not work fully

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-168?page=history ]

Brett Porter reassigned MNG-168:
--------------------------------

    Assign To: Brett Porter

> dependency management for scope did not work fully
> --------------------------------------------------
>
>          Key: MNG-168
>          URL: http://jira.codehaus.org/browse/MNG-168
>      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 take.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira