[
https://issues.apache.org/jira/browse/MEJB-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966079#comment-17966079
]
Olivier Lamy commented on MEJB-19:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-ejb-plugin#62|https://github.com/apache/maven-ejb-plugin/issues/62].
> clientExclude(s) does not work
> ------------------------------
>
> Key: MEJB-19
> URL: https://issues.apache.org/jira/browse/MEJB-19
> Project: Maven EJB Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Maven 2.0.4
> Reporter: Stefan Seidel
> Priority: Major
> Fix For: 2.1
>
>
> I've tried each and every configuration of <clientExcludes> and
> <clientIncludes> to control what is being put into the ejb-client JAR, but
> nothing really works. I expect the configuration
> <clientExcludes>
> <clientExclude>**</clientExclude>
> </clientExcludes>
> to produce an empty JAR - but it doesn't.
> What I really need to do is to exclude ejb-jar.xml and jboss.xml from the
> client jar because JBoss 4 will still (try to) deploy the JAR file because
> these XMLs are in it, even if it is given as java module in the
> application.xml. Leaving these files there leads the whole idea of a client
> JAR ad adsurdum.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
