Re: Tip about Skinny Wars

[Martin Höller]

On Tuesday 01 July 2008 Michael McCallum wrote:
> > On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller <[EMAIL PROTECTED]> wrote:
> > > I think I found one BIG problem with your workaround: it only works
> > > if you already have (the latest version of) your WAR's pom.xml file
> > > in the repository, otherwise maven 2.0.9 reports a missing
> > > dependency.
> > >
> > > So this approach is not useable with the maven-release-plugin :-(
>
> Rubbish i use this all the time with 2.0.9 without any problems. Have
> been since 2.0.5 and for at least for the last 6 months.

Did you try the sample project I posted? What are your results?

> It might be because I use ranges for deps though, and I don't use
> modules.

So you don't have a multimodule project? Well, that's what I was talking 
about! In a single-module project your declared dependencies have to be in 
a (local  or remote) repository anyway.

- martin


signature.asc
Description: This is a digitally signed message part.

Re: Tip about Skinny Wars

[Michael McCallum]

> On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller <[EMAIL PROTECTED]> wrote:
> > I think I found one BIG problem with your workaround: it only works if
> > you already have (the latest version of) your WAR's pom.xml file in the
> > repository, otherwise maven 2.0.9 reports a missing dependency.
> >
> > So this approach is not useable with the maven-release-plugin :-(
> >
Rubbish i use this all the time with 2.0.9 without any problems. Have been 
since 2.0.5 and for at least for the last 6 months.

It might be because I use ranges for deps though, and I don't use modules.

-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tip about Skinny Wars

[Arnaud HERITIER]

My workaround is more a hack that something else.
It's not really logical to have in a project to dependencies to a pom and a
war of a same artifact.
This is certainly a bug in the core of maven which doesn't support it :-(
I'm trying to see how I can change the ear plugin to fix this issue.

Arnaud

On Tue, Jul 1, 2008 at 2:58 PM, Martin Höller <[EMAIL PROTECTED]> wrote:

> Hi Arnaud!
>
> I think I found one BIG problem with your workaround: it only works if you
> already have (the latest version of) your WAR's pom.xml file in the
> repository, otherwise maven 2.0.9 reports a missing dependency.
>
> So this approach is not useable with the maven-release-plugin :-(
>
> I made up a simple test project consisting of a parent and three modules:
> myJar, myWar, and myEar. myEar depends on myWar and myWar depends on myJar.
> With your approach and an empty repository the build fails due to a missing
> myWar:pom dependency.
>
> As I think this list doesn't allow attachments I've made the sample
> available at 
> http://www.xss.co.at/~martin/tmp/m2-skinny-war-demo.tar.bz2
>
> A 'mvn package' fails, while a 'mvn install' succeeds.
>
> Any comments?
>
> - martin
>
> On Tuesday 03 June 2008 Arnaud HERITIER wrote:
> > Hi all,
> >
> >   I would like to share with you a workaround I found for the problem of
> > transitive dependencies in skinny wars.
> >   In the documentation it is said that :
> >  "Now the painful part.  Your EAR's <<>> needs to list every
> > dependency that the WAR has.
> >  This is because Maven assumes fat WARs and does not include transitive
> > dependencies
> >  of WARs within the EAR."
> >
> >   A workaround of this is to define for each war 2 dependencies. One for
> > the war itself and another for the war's pom to retrieve transitive
> > dependencies.
> >   With that you'll have something like that in your ear dependencies :
> >
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > war
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > pom
> > 
> > 
> >
> > I'm using maven 2.0.9.
> >
> > I'll do more tests tomorrow and I'll update the doc :
> >
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.htm
> >l
> >
> > Cheers
> >
> > arnaud
>
>
>

Re: Tip about Skinny Wars

[Martin Höller]

Hi Arnaud!

I think I found one BIG problem with your workaround: it only works if you 
already have (the latest version of) your WAR's pom.xml file in the 
repository, otherwise maven 2.0.9 reports a missing dependency.

So this approach is not useable with the maven-release-plugin :-(

I made up a simple test project consisting of a parent and three modules: 
myJar, myWar, and myEar. myEar depends on myWar and myWar depends on myJar. 
With your approach and an empty repository the build fails due to a missing 
myWar:pom dependency.

As I think this list doesn't allow attachments I've made the sample 
available at http://www.xss.co.at/~martin/tmp/m2-skinny-war-demo.tar.bz2

A 'mvn package' fails, while a 'mvn install' succeeds.

Any comments?

- martin

On Tuesday 03 June 2008 Arnaud HERITIER wrote:
> Hi all,
>
>   I would like to share with you a workaround I found for the problem of
> transitive dependencies in skinny wars.
>   In the documentation it is said that :
>  "Now the painful part.  Your EAR's <<>> needs to list every
> dependency that the WAR has.
>  This is because Maven assumes fat WARs and does not include transitive
> dependencies
>  of WARs within the EAR."
>
>   A workaround of this is to define for each war 2 dependencies. One for
> the war itself and another for the war's pom to retrieve transitive
> dependencies.
>   With that you'll have something like that in your ear dependencies :
>
> 
> 
> com.acme
> war1
> 1.0.0
> war
> 
> 
> com.acme
> war1
> 1.0.0
> pom
> 
> 
>
> I'm using maven 2.0.9.
>
> I'll do more tests tomorrow and I'll update the doc :
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.htm
>l
>
> Cheers
>
> arnaud




signature.asc
Description: This is a digitally signed message part.

Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Lee Meador]

Maybe I'm missing something but I thought the purpose of a "skinny war" was
to consolidate shared dependencies between several wars and some ejb jars.

If the new feature will build a jar in the same project as the war and that
jar contains dependencies there has to be some other feature that takes
several of those spare jars, generated a union on the contents and puts that
into the ear somewhere.

So do both of these new features exist in some yet-to-be-released plugin
version or just the one that collects up the dependency jars?

Thanks.

--- Lee

On Wed, Jun 4, 2008 at 11:23 AM, Arnaud HERITIER <[EMAIL PROTECTED]>
wrote:

> ok I didn't think about that.
> It can be a usable workaround.
>
> Thx
>
> Arnaud
>
> On Wed, Jun 4, 2008 at 6:08 PM, Jörg Schaible <
> [EMAIL PROTECTED]> wrote:
>
> > Hi Arnaud,
> >
> > Arnaud HERITIER wrote:
> > > I think it is not the same problem.
> > > MWAR-131 is about to reuse classes defined in a war.
> > > attachClasses will generate a secondary artifact that we'll be able
> > > to reuse as dependency in another project.
> >
> > Yes, this "other project" might be the ear ...
> >
> > > The problem for skinny WARs is that EARs didn't package WARs
> > > transitive dependencies.
> > > It's not about classes bundled in the war (which are always in the
> > > war).
> >
> > ... and the attached jar will transport the transitive deps.
> >
> > - Jörg
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>



-- 
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Arnaud HERITIER]

ok I didn't think about that.
It can be a usable workaround.

Thx

Arnaud

On Wed, Jun 4, 2008 at 6:08 PM, Jörg Schaible <
[EMAIL PROTECTED]> wrote:

> Hi Arnaud,
>
> Arnaud HERITIER wrote:
> > I think it is not the same problem.
> > MWAR-131 is about to reuse classes defined in a war.
> > attachClasses will generate a secondary artifact that we'll be able
> > to reuse as dependency in another project.
>
> Yes, this "other project" might be the ear ...
>
> > The problem for skinny WARs is that EARs didn't package WARs
> > transitive dependencies.
> > It's not about classes bundled in the war (which are always in the
> > war).
>
> ... and the attached jar will transport the transitive deps.
>
> - Jörg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Jörg Schaible]

Hi Arnaud,

Arnaud HERITIER wrote:
> I think it is not the same problem.
> MWAR-131 is about to reuse classes defined in a war.
> attachClasses will generate a secondary artifact that we'll be able
> to reuse as dependency in another project.

Yes, this "other project" might be the ear ...

> The problem for skinny WARs is that EARs didn't package WARs
> transitive dependencies.
> It's not about classes bundled in the war (which are always in the
> war). 

... and the attached jar will transport the transitive deps.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Arnaud HERITIER]

I think it is not the same problem.
MWAR-131 is about to reuse classes defined in a war.
attachClasses will generate a secondary artifact that we'll be able to reuse
as dependency in another project.

The problem for skinny WARs is that EARs didn't package WARs transitive
dependencies.
It's not about classes bundled in the war (which are always in the war).

Arnaud

On Wed, Jun 4, 2008 at 4:20 PM, Mark Struberg <[EMAIL PROTECTED]> wrote:

> Hi Arnaud!
>
> The maven-war-plugin already has a similar mechanism with
> true, but this hasn't yet been released.
> As I wrote in my previous mail: see MWAR-131 (and partly obsolete MWAR-73)
> for further details.
>
> This workaround should also work in conjunction with the maven-ear-plugin.
>
> LieGrü,
> strub
>
> --- Arnaud HERITIER <[EMAIL PROTECTED]> schrieb am Mi, 4.6.2008:
>
> > Von: Arnaud HERITIER <[EMAIL PROTECTED]>
> > Betreff: Re: Tip about Skinny Wars - is an enforcer plugin's bug side
> effect :-(
> > An: "Maven Users List" 
> > CC: "Maven Developers List" <[EMAIL PROTECTED]>
> > Datum: Mittwoch, 4. Juni 2008, 15:28
> > I made additional tests and I found that it is another side
> > effect of the
> > usage of the enforcer plugin (build from trunk rev 651824).
> >
> > :-(
> >
> > I will have a look at its code to see if this bug of the
> > enforcer plugin can
> > become a feature in the war plugin ;-)
> >
> > Arnaud
> >
> > On Tue, Jun 3, 2008 at 7:31 PM, Arnaud HERITIER
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Hi all,
> > >
> > >   I would like to share with you a workaround I found
> > for the problem of
> > > transitive dependencies in skinny wars.
> > >   In the documentation it is said that :
> > >  "Now the painful part.  Your EAR's
> > <<>> needs to list every
> > > dependency that the WAR has.
> > >  This is because Maven assumes fat WARs and does not
> > include transitive
> > > dependencies
> > >  of WARs within the EAR."
> > >
> > >   A workaround of this is to define for each war 2
> > dependencies. One for
> > > the war itself and another for the war's pom to
> > retrieve transitive
> > > dependencies.
> > >   With that you'll have something like that in
> > your ear dependencies :
> > >
> > > 
> > > 
> > > com.acme
> > > war1
> > > 1.0.0
> > > war
> > > 
> > > 
> > > com.acme
> > > war1
> > > 1.0.0
> > > pom
> > > 
> > > 
> > >
> > > I'm using maven 2.0.9.
> > >
> > > I'll do more tests tomorrow and I'll update
> > the doc :
> > >
> >
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> > >
> > > Cheers
> > >
> > > arnaud
> > >
> > >
> > >
>
>
>   __
> Gesendet von Yahoo! Mail.
> Dem pfiffigeren Posteingang.
> http://de.overview.mail.yahoo.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Mark Struberg]

Hi Arnaud!

The maven-war-plugin already has a similar mechanism with 
true, but this hasn't yet been released. 
As I wrote in my previous mail: see MWAR-131 (and partly obsolete MWAR-73) for 
further details.

This workaround should also work in conjunction with the maven-ear-plugin.

LieGrü,
strub

--- Arnaud HERITIER <[EMAIL PROTECTED]> schrieb am Mi, 4.6.2008:

> Von: Arnaud HERITIER <[EMAIL PROTECTED]>
> Betreff: Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect 
> :-(
> An: "Maven Users List" 
> CC: "Maven Developers List" <[EMAIL PROTECTED]>
> Datum: Mittwoch, 4. Juni 2008, 15:28
> I made additional tests and I found that it is another side
> effect of the
> usage of the enforcer plugin (build from trunk rev 651824).
> 
> :-(
> 
> I will have a look at its code to see if this bug of the
> enforcer plugin can
> become a feature in the war plugin ;-)
> 
> Arnaud
> 
> On Tue, Jun 3, 2008 at 7:31 PM, Arnaud HERITIER
> <[EMAIL PROTECTED]> wrote:
> 
> > Hi all,
> >
> >   I would like to share with you a workaround I found
> for the problem of
> > transitive dependencies in skinny wars.
> >   In the documentation it is said that :
> >  "Now the painful part.  Your EAR's
> <<>> needs to list every
> > dependency that the WAR has.
> >  This is because Maven assumes fat WARs and does not
> include transitive
> > dependencies
> >  of WARs within the EAR."
> >
> >   A workaround of this is to define for each war 2
> dependencies. One for
> > the war itself and another for the war's pom to
> retrieve transitive
> > dependencies.
> >   With that you'll have something like that in
> your ear dependencies :
> >
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > war
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > pom
> > 
> > 
> >
> > I'm using maven 2.0.9.
> >
> > I'll do more tests tomorrow and I'll update
> the doc :
> >
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> >
> > Cheers
> >
> > arnaud
> >
> >
> >


  __
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(

[Arnaud HERITIER]

I made additional tests and I found that it is another side effect of the
usage of the enforcer plugin (build from trunk rev 651824).

:-(

I will have a look at its code to see if this bug of the enforcer plugin can
become a feature in the war plugin ;-)

Arnaud

On Tue, Jun 3, 2008 at 7:31 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:

> Hi all,
>
>   I would like to share with you a workaround I found for the problem of
> transitive dependencies in skinny wars.
>   In the documentation it is said that :
>  "Now the painful part.  Your EAR's <<>> needs to list every
> dependency that the WAR has.
>  This is because Maven assumes fat WARs and does not include transitive
> dependencies
>  of WARs within the EAR."
>
>   A workaround of this is to define for each war 2 dependencies. One for
> the war itself and another for the war's pom to retrieve transitive
> dependencies.
>   With that you'll have something like that in your ear dependencies :
>
> 
> 
> com.acme
> war1
> 1.0.0
> war
> 
> 
> com.acme
> war1
> 1.0.0
> pom
> 
> 
>
> I'm using maven 2.0.9.
>
> I'll do more tests tomorrow and I'll update the doc :
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
>
> Cheers
>
> arnaud
>
>
>

Re: Tip about Skinny Wars

[Nigel Magnay]

FWIW, I used a slightly different approach in the cargo uberwar plugin
(which generates a War-of-Wars). I made it look at the WAR
dependencies, and create a 'phantom' pom projects in the repository,
which can then be passed to the "normal" maven dependency
reconciliation framework to work out what JARs ought to end up in
/WEB-INF/lib.

I consider it a totally hacky solution, but avoids having to make your
dependent WAR files 'special' in any way. The root problem is that in
maven 2.0.x, it's really hard to use the dependency resolution stuff
outside the 'default' way (the WAR=no transitive dependencies is burnt
into the WAR metatype, so nothing is considered for resolution beyond
that point). I'm told this is being fixed in 2.1, but I haven't
checked for about 6 months to see if there's any progress.

On Wed, Jun 4, 2008 at 11:07 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Not totally.
> It can fix : Automatically inherit transitive dependencies from the war
> artifact (the default Maven behaviour is not to inherit transitively from
> war dependencies).
> But not : Develop with classes included in the war artifact /WEB-INF/classes
> directory by including them in the project classpath.
>
> Arnaud
>
> On Wed, Jun 4, 2008 at 11:17 AM, Milos Kleint <[EMAIL PROTECTED]> wrote:
>
>> i'm wondering if the solution would render the war-path plugin
>> obsolete? it's causing trouble in embedded use.
>> http://issues.appfuse.org/browse/APF-645
>>
>> Milos
>>
>> On 6/3/08, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>> > Hi all,
>> >
>> >   I would like to share with you a workaround I found for the problem of
>> >  transitive dependencies in skinny wars.
>> >   In the documentation it is said that :
>> >   "Now the painful part.  Your EAR's <<>> needs to list every
>> >  dependency that the WAR has.
>> >   This is because Maven assumes fat WARs and does not include transitive
>> >  dependencies
>> >   of WARs within the EAR."
>> >
>> >   A workaround of this is to define for each war 2 dependencies. One for
>> the
>> >  war itself and another for the war's pom to retrieve transitive
>> >  dependencies.
>> >   With that you'll have something like that in your ear dependencies :
>> >
>> > 
>> > 
>> > com.acme
>> > war1
>> > 1.0.0
>> > war
>> > 
>> > 
>> > com.acme
>> > war1
>> > 1.0.0
>> > pom
>> > 
>> > 
>> >
>> >  I'm using maven 2.0.9.
>> >
>> >  I'll do more tests tomorrow and I'll update the doc :
>> >
>> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
>> >
>> >  Cheers
>> >
>> >
>> >  arnaud
>> >
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tip about Skinny Wars

[Arnaud HERITIER]

Not totally.
It can fix : Automatically inherit transitive dependencies from the war
artifact (the default Maven behaviour is not to inherit transitively from
war dependencies).
But not : Develop with classes included in the war artifact /WEB-INF/classes
directory by including them in the project classpath.

Arnaud

On Wed, Jun 4, 2008 at 11:17 AM, Milos Kleint <[EMAIL PROTECTED]> wrote:

> i'm wondering if the solution would render the war-path plugin
> obsolete? it's causing trouble in embedded use.
> http://issues.appfuse.org/browse/APF-645
>
> Milos
>
> On 6/3/08, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> >   I would like to share with you a workaround I found for the problem of
> >  transitive dependencies in skinny wars.
> >   In the documentation it is said that :
> >   "Now the painful part.  Your EAR's <<>> needs to list every
> >  dependency that the WAR has.
> >   This is because Maven assumes fat WARs and does not include transitive
> >  dependencies
> >   of WARs within the EAR."
> >
> >   A workaround of this is to define for each war 2 dependencies. One for
> the
> >  war itself and another for the war's pom to retrieve transitive
> >  dependencies.
> >   With that you'll have something like that in your ear dependencies :
> >
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > war
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > pom
> > 
> > 
> >
> >  I'm using maven 2.0.9.
> >
> >  I'll do more tests tomorrow and I'll update the doc :
> >
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> >
> >  Cheers
> >
> >
> >  arnaud
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Tip about Skinny Wars

[Mark Struberg]

Imho this is a very good solution if your WAR really is a very skinny one, ie 
has no content in WEB-INF/lib and WEB-INF/classes AND you like to have all the 
jars in your EAR (common libs for all WARs) rather than in the single WAR.

If one of the WARs does contain libs, you may end up with having different 
versions of the same jar in your final EAR.

At the end of the day, one should be able to configure on the EAR level which 
lib is common for all WARs (APP-INF/lib) and removed from all WARs WEB-INF/lib 
folders The rest should be skipped and left back in the WARs.

With the warpath plugin, Michael Horwitz originally addressed the WAR-overlay 
problem, so altough there are a few common points, it mostly covers WAR-WAR and 
not WAR-EAR dependencies. 
There are a few comments on this topic in MWAR-73 and MWAR-131.

LieGrü,
strub

--- Milos Kleint <[EMAIL PROTECTED]> schrieb am Mi, 4.6.2008:

> Von: Milos Kleint <[EMAIL PROTECTED]>
> Betreff: Re: Tip about Skinny Wars
> An: "Maven Users List" 
> Datum: Mittwoch, 4. Juni 2008, 11:17
> i'm wondering if the solution would render the war-path
> plugin
> obsolete? it's causing trouble in embedded use.
> http://issues.appfuse.org/browse/APF-645
> 
> Milos
> 
> On 6/3/08, Arnaud HERITIER <[EMAIL PROTECTED]>
> wrote:
> > Hi all,
> >
> >   I would like to share with you a workaround I found
> for the problem of
> >  transitive dependencies in skinny wars.
> >   In the documentation it is said that :
> >   "Now the painful part.  Your EAR's
> <<>> needs to list every
> >  dependency that the WAR has.
> >   This is because Maven assumes fat WARs and does not
> include transitive
> >  dependencies
> >   of WARs within the EAR."
> >
> >   A workaround of this is to define for each war 2
> dependencies. One for the
> >  war itself and another for the war's pom to
> retrieve transitive
> >  dependencies.
> >   With that you'll have something like that in
> your ear dependencies :
> >
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > war
> > 
> > 
> > com.acme
> > war1
> > 1.0.0
> > pom
> > 
> > 
> >
> >  I'm using maven 2.0.9.
> >
> >  I'll do more tests tomorrow and I'll update
> the doc :
> > 
> http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
> >
> >  Cheers
> >
> >
> >  arnaud
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]


  __
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tip about Skinny Wars

[Milos Kleint]

i'm wondering if the solution would render the war-path plugin
obsolete? it's causing trouble in embedded use.
http://issues.appfuse.org/browse/APF-645

Milos

On 6/3/08, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi all,
>
>   I would like to share with you a workaround I found for the problem of
>  transitive dependencies in skinny wars.
>   In the documentation it is said that :
>   "Now the painful part.  Your EAR's <<>> needs to list every
>  dependency that the WAR has.
>   This is because Maven assumes fat WARs and does not include transitive
>  dependencies
>   of WARs within the EAR."
>
>   A workaround of this is to define for each war 2 dependencies. One for the
>  war itself and another for the war's pom to retrieve transitive
>  dependencies.
>   With that you'll have something like that in your ear dependencies :
>
> 
> 
> com.acme
> war1
> 1.0.0
> war
> 
> 
> com.acme
> war1
> 1.0.0
> pom
> 
> 
>
>  I'm using maven 2.0.9.
>
>  I'll do more tests tomorrow and I'll update the doc :
>  http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
>
>  Cheers
>
>
>  arnaud
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: Tip about Skinny Wars

[Baeriswyl Kuno - Extern (IT-BA-MV)]

Hello,

looks interesting. Are there any comments or recommendations from the Maven 
Team?
Thanks for sharing.
Kuno

-Ursprüngliche Nachricht-
Von: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 3. Juni 2008 19:31
An: Maven Users List
Betreff: Tip about Skinny Wars


Hi all,

  I would like to share with you a workaround I found for the problem of 
transitive dependencies in skinny wars.
  In the documentation it is said that :
 "Now the painful part.  Your EAR's <<>> needs to list every 
dependency that the WAR has.  This is because Maven assumes fat WARs and does 
not include transitive dependencies  of WARs within the EAR."

  A workaround of this is to define for each war 2 dependencies. One for the 
war itself and another for the war's pom to retrieve transitive dependencies.
  With that you'll have something like that in your ear dependencies :



com.acme
war1
1.0.0
war


com.acme
war1
1.0.0
pom



I'm using maven 2.0.9.

I'll do more tests tomorrow and I'll update the doc : 
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html

Cheers

arnaud

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tip about Skinny Wars

[Arnaud HERITIER]

Hi all,

  I would like to share with you a workaround I found for the problem of
transitive dependencies in skinny wars.
  In the documentation it is said that :
 "Now the painful part.  Your EAR's <<>> needs to list every
dependency that the WAR has.
 This is because Maven assumes fat WARs and does not include transitive
dependencies
 of WARs within the EAR."

  A workaround of this is to define for each war 2 dependencies. One for the
war itself and another for the war's pom to retrieve transitive
dependencies.
  With that you'll have something like that in your ear dependencies :



com.acme
war1
1.0.0
war


com.acme
war1
1.0.0
pom



I'm using maven 2.0.9.

I'll do more tests tomorrow and I'll update the doc :
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html

Cheers

arnaud