[
https://jira.codehaus.org/browse/MEAR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285167#comment-285167
]
Dennis Lundberg commented on MEAR-87:
-------------------------------------
I found another approach to solve this issue that I feel works better.
It uses the same method that Maven WAR Plugin has, with packagingExcludes and
packagingIncludes. These each take a comma-separated String of file patterns.
This was added in
[r1211419|http://svn.apache.org/viewvc?view=revision&revision=1211419].
A new 2.7-SNAPSHOT has been deployed. Please give it a try.
You can look at the ITs that were added in that check-in for examples of how to
configure it. I'll write up some documentation and add it to the site later on.
> Allow exclusion of artifacts when building the ear file.
> --------------------------------------------------------
>
> Key: MEAR-87
> URL: https://jira.codehaus.org/browse/MEAR-87
> Project: Maven 2.x Ear Plugin
> Issue Type: New Feature
> Affects Versions: 2.3.1
> Reporter: Dieter Houthooft
> Assignee: Dennis Lundberg
> Priority: Minor
> Fix For: 2.7
>
> Attachments: maven-ear-plugin-excludes-fixed.patch,
> maven-ear-plugin-excludes.patch
>
>
> What is included in the .ear file is determined by the module list and the
> dependency list and its transitive dependencies. We are often confronted with
> changing demands about what to include in our ear files. It is quite hard to
> change our dependency management (scopes) every time without side-effects on
> other distributable artifacts. So I created an exclude configuration option
> which allows to exclude artifacts from the ear file based on regular
> expressions (java.util.regex) matching artifactIds and groupIds.
> Use it like this:
> <configuration>
> <excludes>
> <exclude>
> <groupId>be.nondistributable.*</groupId>
> </exclude>
> </excludes>
> </configuration>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
