Re: Tip about Skinny Wars - is an enforcer plugin's bug side effect :-(
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 :-(
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 :-(
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 :-(
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 :-(
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 :-(
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 > > >
