[
http://jira.codehaus.org/browse/MASSEMBLY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158031#action_158031
]
John Casey commented on MASSEMBLY-299:
--------------------------------------
Do you have a test project that I can use to verify/verify the fix for this?
Without a little more information about how this is reproduced, it'll be very
difficult to fix.
> 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
>
> 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
