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
