Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0
-
Fix Version/s: 2.1
-
Component/s: None
-
Labels:None
-
Environment:Maven 2.0.4
-
Number of attachments :
Description
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.
Issue Links
| This issue is depended upon by: | ||||
| MEJB-16 | clientExcludes generates empty packages i client-jar |
|
|
|
Seems to be fixed in 2.1-SNAPSHOT.