You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Clive Jevons (JIRA)" <ji...@codehaus.org> on 2008/07/07 21:31:26 UTC
[jira] Commented: (MASSEMBLY-190) Problem with dependency conflict
resolution on multi-module project
[ http://jira.codehaus.org/browse/MASSEMBLY-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140972#action_140972 ]
Clive Jevons commented on MASSEMBLY-190:
----------------------------------------
Has there been any progress on this? Is there a known workaround? I've currently got this problem in 2.0.9 with a WAR assembly.
My WAR includes the ejb-client. But by doing so, I transitively include all the dependencies the ejb (not the client) needs. So I 'exclusion' them from the WAR. If I build just the WAR, this works find. If I build the WAR as part of the aggregate build, then the exclusions are ignored and I end up having all of the dependencies I'd excluded in WEB-INF/lib
Cheers,
C
> Problem with dependency conflict resolution on multi-module project
> -------------------------------------------------------------------
>
> Key: MASSEMBLY-190
> URL: http://jira.codehaus.org/browse/MASSEMBLY-190
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Environment: Using maven 2.0.5 and assembly 2.2-SNAPSHOT
> Reporter: Frédéric ESNAULT
> Fix For: 2.2-beta-3
>
>
> Hi,
> I'm trying to use the assembly plugin to gather all the jars of my project, including all dependencies.
> As the project is composed of several modules, I use a descriptor which looks like this :
> <assembly>
> <id>bin</id>
> <formats>
> <format>zip</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <moduleSets>
> <moduleSet>
> <binaries>
> <outputDirectory>/</outputDirectory>
> <unpack>false</unpack>
> <includeDependencies>true</includeDependencies>
> </binaries>
> </moduleSet>
> </moduleSets>
> </assembly>
> It seems to work fine at first sight - it creates a zip containing all the jar files. However, I find in the archive several instances of the same dependency with differents versions, for instance asm-1.5.3 and asm-2.2.3. This is a surprise as maven is supposed to take care of conflict resolution.
> When I look at a detailed trace, it appears that conflict resolution is done but on each module independently. But my modules are intended to work together and I expect to get an assembly with only one version of each dependency found on the whole set of mudules. It seems to me that conflict resolution is not managed properly in this use case.
--
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