maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Work started: (MASSEMBLY-190) Problem with dependency conflict resolution on multi-module project
Date Mon, 22 Sep 2008 22:12:46 GMT


Work on MASSEMBLY-190 started by John Casey.

> Problem with dependency conflict resolution on multi-module project
> -------------------------------------------------------------------
>                 Key: MASSEMBLY-190
>                 URL:
>             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
>            Assignee: John Casey
>             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:
For more information on JIRA, see:


View raw message