Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2-beta-2
-
None
-
None
-
Win2003/Cygwin Maven 2.0.8
Description
There are a lot of things wrong with includes/excludes and types in DependencySets. Basically, it needs to be completely regression tested as it completely does not work right in many ways.
group:artifact:type
In describing type, its ignored. When I put zip for type, I can get ear files. When I exclude all com.* artifacts then include my own com.mydotcom.* - I actually get double the ears in my resulting zip artifact. Example below:
<dependencySets>
<dependencySet>
<outputDirectory>/opt/jboss/server/default/deploy/</outputDirectory>
<excludes>
<exclude>com:*</exclude>
</excludes>
</dependencySet>
<dependencySet>
<outputDirectory>/opt/jboss/server/default/deploy/</outputDirectory>
<includes>
<include>com.mydotcom:*:ear</include>
</includes>
</dependencySet>
</dependencySets>
In general, there seems to be issue with the wild card. Putting com.mydotcom::zip - once the * is hit, everything after it is ignored. However, for <include> putting com::zip does work correctly - oddly enough. It correctly does NOT give me ear files. When I put com::ear I correctly get ears. When I put com.mydotcom::zip, then I incorrectly get all ears. Lots of inconsistencies here and odd behavior.
Here is a good document on includes/excludes. Unfortunately, this does not work right. I'd suggest excludes/includes be completely re-looked at. Thanks!!!
http://www.sonatype.com/book/reference/assemblies.html#d0e13207