Hi Richard and Wouter,
Good to hear from you. From Richard post to NetBean below, looks the issue
has a workaround and need a new feature to enhance. Looks there is no
GlassFish
issue here. Great job and thank you to both of you!
Judy
--------
There is a simple solution to solve this.
Add the following to the Maven pom.xml
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
Obviously not bundling all the libs with the project is a feature, but
it is an advanced feature.
I propose adding a feature request for NetBeans to add a tick box when
creating a Maven EJB to add this Maven plugin.
Richard Kolb wrote:
>
>
> On 16 March 2010 11:29, Wouter van Reeven <wouter_at_van.reeven.nl
> <mailto:wouter_at_van.reeven.nl>> wrote:
>
> On Tue, Mar 16, 2010 at 11:08:40AM +0200, Richard Kolb wrote:
> > That's the thing, it works 100%, because Netbeans packages the
> JAR differently
> > to Maven
> > The log4j-1.2.15.jar is included in the root of the EJB JAR
> >
> > In the original mail I compared the two ways. One maven, the
> other NB 6.8
> > native
>
> OK I can verify that. That looks like a bug in the maven-ejb-plugin to
> me. Maybe we can discuss this further on the NetBeans Maven
> mailinglist,
> since it looks like a NetBeans issue.
>
>
> Cool.
> http://netbeans.org/projects/www/lists/nbusers/archive/2010-03/message/812
> just to be clear the bug is in the ejb Maven packaging and not in the
> maven-ejb-plugin.
> The maven-ejb-plugin fixes the issue, (or works around it)
>
>
>
>
> regards
> Richard.
>
>