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 <<<pom.xml>>> 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 : > > <dependencies> > <dependency> > <groupId>com.acme</groupId> > <artifactId>war1</artifactId> > <version>1.0.0</version> > <type>war</type> > </dependency> > <dependency> > <groupId>com.acme</groupId> > <artifactId>war1</artifactId> > <version>1.0.0</version> > <type>pom</type> > </dependency> > </dependencies> > > 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 > > >
