assembly-plugin behaviour for duplicate dependency (but with different version)

[aldana <al...@gmx.de>]

hi,

i am using dependency analyzer to pack my app. currently i want to remove
some not-needed dependencies. what happened was that respective dependency
was not included any longer but instead the same dependency but with
different version got packed.

so i guess that assembly plugin includes only one library with a certain
groupId:artifactId. if it resolves two dependencies with same
groupId:artifactId it only includes the latest one.

am i right with this assumption? 

i got a custom assembly-distribution file (never the less it only slightly
differs from the standard one -> outputFileNameMapping is different):

<assembly>
  <id>binary</id>
  <formats>
    <format>zip</format>
  </formats>
  <includeBaseDirectory>false</includeBaseDirectory>
  <baseDirectory>all</baseDirectory>
  <fileSets>
    <fileSet>
      <includes>
        <include>*.jar</include>
      </includes>
      <excludes>
        <exclude>*-sources.jar</exclude>
      </excludes>
      <directory>${basedir}/target</directory>      
      <outputDirectory></outputDirectory>
      <lineEnding>keep</lineEnding>
      <fileMode>0644</fileMode>
    </fileSet>
  </fileSets>
  <dependencySets>
    <dependencySet>
     
<outputFileNameMapping>${groupId}-${artifactId}-${version}.${extension}</outputFileNameMapping>
      <outputDirectory>lib</outputDirectory>
    </dependencySet>
  </dependencySets>
</assembly> 





-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
-- 
View this message in context: http://www.nabble.com/assembly-plugin-behaviour-for-duplicate-dependency-%28but-with-different-version%29-tp16718250s177p16718250.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org