-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lee Meador
Sent: Thursday, May 04, 2006 8:12 PM
To: Maven Users List
Subject: Re: M2 - Best practice for common jars between EJB,WAR modules
in EAR
I've got two ejb jars, a few wars and they are all
Sent: Thursday, May 04, 2006 8:12 PM
To: Maven Users List
Subject: Re: M2 - Best practice for common jars between EJB,WAR modules
in EAR
I've got two ejb jars, a few wars and they are all in an ear.
I'm using Webshere 6.
I do the same thing you do but exclude the jars from the wars. There
used
I've got two ejb jars, a few wars and they are all in an ear.
I'm using Webshere 6.
I do the same thing you do but exclude the jars from the wars. There used to
be a bug where you could exclude everything from the war or nothing. Maybe
that is fixed and you can exclude piecemeal. I got by by
I'm not sure if this works in JBoss, but the way I'm doing it in Weblogic is
slightly different, so might be worth trying just on the off chance...
I've got an EAR, which contains an EJB jar, a number of WARs and a number of
common jars, all in the root. The common jars are referenced in the
:[EMAIL PROTECTED]
Sent: Wednesday, March 22, 2006 1:47 PM
To: Maven Users List
Subject: Re: M2 - Best practice for common jars between EJB,WAR modules
in EAR
Richard,
I feel your pain. I struggled with similar issues at great length
several weeks back. On one hand, Maven's encouragement toward
Hi,
Just a quick question, unrelated to your problem (sorry), but is it default
Maven behaviour to explode the dependencies of a WAR in to the
WEB-INF/classes directory within the WAR?
Thanks,
Gareth
On 3/23/06, Richard Sladek [EMAIL PROTECTED] wrote:
I agree in that it is a good idea of
Just a quick question, unrelated to your problem (sorry), but is it default
Maven behaviour to explode the dependencies of a WAR in to the
WEB-INF/classes directory within the WAR?
Afaik, yes, it is. But not to the WEB-INF/classes, but WEB-INF/lib folder.
--
View this message in context:
I agree in that it is a good idea of treating wars as self-contained archives
and if deployed on its own, this is even required, in fact. However, there
is a little bit different situation when deploying war within an ear (which
is pretty common). In such a case I consider the idea of skeleton
@maven.apache.org
Onderwerp: Re: M2 - Best practice for common jars between EJB,WAR
modules in EAR
I have just one more question:
might such duplicates in ear modules cause some classloader issues (or
anything) or is it completely safe to have them
Onderwerp: Re: M2 - Best practice for common jars between EJB,WAR
modules in EAR
I have just one more question:
might such duplicates in ear modules cause some classloader issues (or
anything) or is it completely safe to have them
the
WAR indeed deployable outside the EAR but in many cases it is not what
you want.
-Oorspronkelijk bericht-
Van: Richard Sladek [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 23 maart 2006 13:43
Aan: users@maven.apache.org
Onderwerp: Re: M2 - Best practice for common jars
Hello,
I've been searching through the archive half of the day but I haven't found
a satisfactory solution to my problem:
I have an EAR including 2 modules: EJB JAR and WAR.
These 2 modules have some common dependencies, lets say mycommonlib.jar.
When I run the packaging on EAR, I get duplicates
I've been wondering this myself and just didn't care enough to
really solve the problem. ;-)
Fortunately the duplicated libs are not very large so it doesn't
affect me much (yet).
Anyone got a solution?
Wayne
On 3/22/06, Richard Sladek [EMAIL PROTECTED] wrote:
Hello,
I've been searching
Richard,
I feel your pain. I struggled with similar issues at great length
several weeks back. On one hand, Maven's encouragement toward
modularity is a good thing, but something that comes with that is
that in handling upstream dependencies, there is no consideration
given to the
14 matches
Mail list logo
