Hi Mike,
I had the same problem, but digging into the Maven code I found that you
have the following line in the dependencies you want to bundle in the WAR:
<metaEntries>
<metaEntry>j2ee.war.bundle.jar:true</metaEntry>
</metaEntries>
For example:
<dependency>
<id>javamail</id>
<version>1.2</version>
<metaEntries>
<metaEntry>j2ee.war.bundle.jar:true</metaEntry>
</metaEntries>
</dependency>
This metaEntry is in Maven b5, but in the CVS HEAD the metaEntry is changed
to war.bundle.jar, I hope this help you.
Edgar
----- Original Message -----
From: "Dickson, Mike" <[EMAIL PROTECTED]>
To: "'Turbine Maven Users List'" <[EMAIL PROTECTED]>
Sent: Monday, August 19, 2002 11:58 AM
Subject: RE: Missing the EAR Goal
Are these modules under development? I could certainly use them also and
the approach you lay out makes sense.
A related question, is there a straightforward way when buildiong a WAR file
to copy the dependencies into the lib directory in WEB-INF? It doesn't seem
to happen automatically as a part of the WAR target.
Mike
> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 19, 2002 11:15 AM
> To: 'Turbine Maven Users List'
> Subject: RE: Missing the EAR Goal
>
> Hi Edgar,
>
> Yes, there is a good reason ! :-)
>
> War is about building Wars, not Ear ... An Ear is a set of J2EE Modules
> : WAR, RAR, EJB-JAR + dependent libraries
>
> The idea (at least my vision :-)), is to have several plugins :
> - one War plugin (to create War modules)
> - one Ejb plugin (to create Ejb jars modules)
> - one Rar plugin (to create Rar modules)
> - one Ear plugin (to create a j2ee application)
> - one or several deploy plugins to deploy Ears to different application
> servers
>
> Hope it helps
> -Vincent
>
> > -----Original Message-----
> > From: Edgar Gonz�lez [mailto:[EMAIL PROTECTED]]
> > Sent: 19 August 2002 15:43
> > To: [EMAIL PROTECTED]
> > Subject: Missing the EAR Goal
> >
> > Hi,
> >
> > Is there any reason to ommit an EAR goal in the war plugin?
> >
> > Edgar
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>