We have noticed some odd behavior related to the maven-assembly-plugin...
With the latest 2.2-SNAPSHOT version of the maven-assembly-plugin, the
ability to define multiple "include" dependencySets and to define
dependencies by any combination of groupId, artifactId, type, and classifier
(using wildcards if necessary) should be available. [Related:
http://jira.codehaus.org/browse/MASSEMBLY-90,
http://jira.codehaus.org/browse/MASSEMBLY-141,
http://jira.codehaus.org/browse/MASSEMBLY-157]
Using the 2.2.-SNAPSHOT version, when we define multiple ZIP file
dependencySet includes and unpack them, it not only includes/expands the
listed included dependencies but also some other [seemingly] unrelated
dependencies. For instance, all of the zip dependencySets below only
contain static web content (html, js, css files) packaged as assemblies from
both WARs and JARs. When we package the assembly below, the result includes
not only the content of the dependencySets listed, but also some other
dependencies (it only includes a couple of the "parent" project
dependencies, which don't seem to be similar or related).
<assembly>
<id>static</id>
<includeBaseDirectory>false</includeBaseDirectory>
<formats>
<format>zip</format>
</formats>
<dependencySets>
<dependencySet>
<outputFileNameMapping></outputFileNameMapping>
<includes>
<include>our.group.id:our.artifact.id.1:zip:static</include>
<include>our.group.id:our.artifact.id.2:zip:static</include>
<include>our.group.id:our.artifact.id.3:zip:static</include>
</includes>
<unpack>true</unpack>
</dependencySet>
</dependencySets>
</assembly>
However, when we define a single include using wildcards and unpack them, it
creates the zip assembly as expected. It includes the project's three
"-static" zip dependencies (as defined above) and no more.
<assembly>
<id>static</id>
<includeBaseDirectory>false</includeBaseDirectory>
<formats>
<format>zip</format>
</formats>
<dependencySets>
<dependencySet>
<outputFileNameMapping></outputFileNameMapping>
<includes>
<include>*:zip:static</include>
</includes>
<unpack>true</unpack>
</dependencySet>
</dependencySets>
</assembly>
I would expect the results of using either of these assembly descriptors to
be the same, but this isn't the case. Is there an explanation for this
behavior, or is this a bug in the way that the assembly filters the
includes/excludes?
--
View this message in context:
http://www.nabble.com/Maven-Assembly-Plugin-tf2583926s177.html#a7203497
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
