11:11 a.m.
I want to add all classes in the ejb/jar follow a pattern:
i.e. all *Bean.class and *Impl.class
There are other classes in the path without that suffix that should not
included.
I use different combinations of includes/excludes and
useDefaultIncludes/useDefaultExcludes
But the result is more or less ALL or NO class in the jar.
I've google and look into the plugin docs but don't find a helpful hint.
Any ideas?
cheers
Wolf
7:58 p.m.
What's your actual use case?
This fragment:
<configuration>
...
<excludes>
<exclude>**/*Impl.class</exclude>
<exclude>**/*Bean.class</exclude>
</excludes>
...
</configuration>
should work.
Steve C
On 26/10/2012, at 3:11 AM, Wolf-Dieter Fink <wfink(a)redhat.com> wrote:
I want to add all classes in the ejb/jar follow a pattern:
i.e. all *Bean.class and *Impl.class
There are other classes in the path without that suffix that should not
included.
I use different combinations of includes/excludes and
useDefaultIncludes/useDefaultExcludes
But the result is more or less ALL or NO class in the jar.
I've google and look into the plugin docs but don't find a helpful hint.
Any ideas?
cheers
Wolf
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
9:05 p.m.
Doh!
You wanted <includes> which does not seem to be supported by the maven-ejb-plugin.
I can think of two other options:
1. Use an ant run plugin task in the prepare-package phase to remove unwanted classes from
${project.build.outputDirectory}/classes
2. Use inclusion filters on the maven-compiler-plugin to compile only the desired classes
from the outset. You would need to be careful of your IDE messing this up for you though.
Adding <includes> to the ejb-plugin looks like a trivial patch for what it's
worth (and the jar plugin supports it).
Steve C
On 27/10/2012, at 11:58 AM, Stephen Coy <steve.coy(a)me.com> wrote:
What's your actual use case?
This fragment:
<configuration>
...
<excludes>
<exclude>**/*Impl.class</exclude>
<exclude>**/*Bean.class</exclude>
</excludes>
...
</configuration>
should work.
Steve C
On 26/10/2012, at 3:11 AM, Wolf-Dieter Fink <wfink(a)redhat.com> wrote:
> I want to add all classes in the ejb/jar follow a pattern:
> i.e. all *Bean.class and *Impl.class
> There are other classes in the path without that suffix that should not
> included.
>
> I use different combinations of includes/excludes and
> useDefaultIncludes/useDefaultExcludes
>
> But the result is more or less ALL or NO class in the jar.
>
> I've google and look into the plugin docs but don't find a helpful hint.
>
>
> Any ideas?
>
> cheers
> Wolf
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:02 a.m.
I guess splitting to different packages isn't appropriate for your case;
so:
I'd try copying the selected classes to a new dir using the resource
plugin,
then pointing the archiver to this dir instead of target/classes .
my2c,
Ondra
On Thu, 2012-10-25 at 18:11 +0200, Wolf-Dieter Fink wrote:
I want to add all classes in the ejb/jar follow a pattern:
i.e. all *Bean.class and *Impl.class
There are other classes in the path without that suffix that should not
included.
I use different combinations of includes/excludes and
useDefaultIncludes/useDefaultExcludes
But the result is more or less ALL or NO class in the jar.
I've google and look into the plugin docs but don't find a helpful hint.
Any ideas?
cheers
Wolf
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4423
days inactive
4425
days old
3 comments
3 participants
participants (3)
-
Ondrej Zizka -
Stephen Coy -
Wolf-Dieter Fink