[
http://jira.codehaus.org/browse/MEJB-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86019
]
Hans Bausewein commented on MEJB-16:
------------------------------------
I've noticed something related.
Say I have a package structure
org/codehaus/*.class
org/codehaus/impl/*.class
and I want to include only the 'org.codehaus' package without the classes in
'org.codehaus.impl'.
I expected I could do:
<clientIncludes>
<clientInclude>org/codehaus/*.class</clientInclude>
</clientIncludes>
but I still got the 'org.codehaus.impl' package classes included.
I had to explicitly exclude the sub package to get rid of them.
> clientExcludes generates empty packages i client-jar
> ----------------------------------------------------
>
> Key: MEJB-16
> URL: http://jira.codehaus.org/browse/MEJB-16
> Project: Maven 2.x Ejb Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Discovered on MAC OSX, but I dont think it is OS
> dependent
> Reporter: Anders Kr. Andersen
> Assigned To: Stephane Nicoll
> Priority: Minor
> Fix For: 2.1
>
>
> When I use the <clientExcludes> ... the excluded packages are still package
> in the jar. But empty.
> The bigggest problem is probably the visual testing the developer is doing.
> Seeing that packages remanis in the jar ... and discovering that they are
> empty simple just takes a little time.
> I don't think the JVM have any problem with this ?
> But I don't think it is in the JAR specification either :-)
--
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
