[jira] Commented: (MASSEMBLY-190) Problem with dependency conflict resolution on multi-module project

["Geoffrey De Smet (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MASSEMBLY-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94069 ] 

Geoffrey De Smet commented on MASSEMBLY-190:
--------------------------------------------

I also have this issue.
I include 2 modules, both have a conflict resolution that ends up on xstream-1.2.1; nevertheless xstream-1.1.3 stil appears in my lib dir.
(I make the jar plugin generate of both modules the classpath in the manifest.MF, both times it's 1.2.1.)

  <moduleSets>
    <moduleSet>
      <includes>
        <include>ggg:ggg-distro</include>
        <include>ggg:ggg-uploader</include>
      </includes>
      <binaries>
        <outputDirectory>/lib</outputDirectory>
        <unpack>false</unpack>
        <fileMode>660</fileMode>
        <dependencySets>
          <dependencySet>
            <!-- HACK om http://jira.codehaus.org/browse/MJAR-28 te fixen -->
            <outputFileNameMapping>${artifactId}-${baseVersion}.${extension}</outputFileNameMapping>
            <scope>runtime</scope>
          </dependencySet>
        </dependencySets>
      </binaries>
    </moduleSet>
  </moduleSets>


> 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
>         Environment: Using maven 2.0.5 and assembly 2.2-SNAPSHOT
>            Reporter: Frédéric ESNAULT
>
> 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