[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=all ]
John Casey closed MASSEMBLY-90.
-------------------------------
Resolution: Fixed
Ok, I've added both of the use cases you mention, and my unit tests seem to
work. FWIW, the artifact filters in question have been factored out into their
own project, to facilitate reuse in other projects.
Give it a spin, and see what you think. The latest snapshot should have these
changes incorporated.
> 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
