You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2010/09/23 01:55:32 UTC

[jira] Closed: (MASSEMBLY-299) assembly does not honnor directives

     [ http://jira.codehaus.org/browse/MASSEMBLY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-299.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2-beta-6
         Assignee: John Casey

> assembly does not honnor <dependencyManagement> directives
> ----------------------------------------------------------
>
>                 Key: MASSEMBLY-299
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-299
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>            Reporter: nicolas de loof
>            Assignee: John Casey
>             Fix For: 2.2-beta-6
>
>
> My project uses many libs and has <dependencyManagement> set to force commons-logging on version 1.1.1
> I still have commons-logging 1.1 in my assembly targ.gz, (with its dependencies : logkit, avalon ...)
> Forcing a dependency to commons-logging 1.1.1 solves this, but this is just a workaround. 
> As the assembly plugin uses "dependencyResolver.resolveDependencies( project, ... " we could expect the dependencyResolver to read the <dependencyManagement>, but this doesn't seem to work as expected.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira