[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=comments#action_79025 ]
Richard van der Hoff commented on MASSEMBLY-90:
-----------------------------------------------
Right, well, that doesn't work any better.
It seems that the pattern is tested against the entire transitive dependency
tree.
On a related note, the following doesn't match anything at all:
{code:xml}
<includes>
<include>!*:so:*</include>
</includes>
{code}
It seems that you need at least one positive pattern in an <includes> or
<excludes> block to make this work.
> add a DependencySet filter based on type
> ----------------------------------------
>
> Key: MASSEMBLY-90
> URL: http://jira.codehaus.org/browse/MASSEMBLY-90
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Reporter: Jason Chaffee
> Assigned To: John Casey
> Fix For: 2.2
>
> Attachments: AbstractAssemblyMojo-patch.txt,
> AbstractAssemblyMojo.java, AbstractAssemblyMojo.java,
> AbstractAssemblyMojo.java, AssemblyClassifierArtifactFilter.java,
> AssemblyTypeArtifactFilter.java, AssemblyTypeArtifactFilter.java,
> component.mdo, component.mdo-patch.txt, descriptor.mdo,
> descriptor.mdo-patch-.txt
>
>
> It would be nice to create a distribution bundle that contains both jars and
> webapps. These would be built by different projects and then an assembly
> project would list these in the pom. However, there is no way to filter the
> dependencies based on their type. This would be be a pretty easy thing to
> add. I have attached a new class, AssemblyTypeArtifactFilter and the
> required change to AbstractAsseblyMojo. The DependencySet class needs to be
> modified as well to add the type field, but I was not able to find it in the
> maven repository.
--
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
