Hello, 2.1-SNAPSHOT of the war plugin only includes dependencies with a runtime scope for exploded,inplace and war goals. I think by default an artifact has a compile scope unless you modify the default scope then it shouldn't be included in the war.
pete marvin Markus Reinhardt wrote: > Hi Sebastien, > > I don't know how the war packaging plugin handles <scope>runtime</scope> > dependencies. I use no <scope> at all for required JARs and > <scope>provided</scope> for those, which should not be packaged inside > the WAR file i.e. are available on your Container. > > How do you build you WAR? > > Markus > > Am Freitag, den 02.06.2006, 07:33 +0200 schrieb Sebastien Arbogast: > > >> I have trouble understanding the new dependency mechanism. I added a >> dependency like this in my root pom dependencyManagament section: >> >> <dependency> >> <groupId>jakarta-regexp</groupId> >> <artifactId>jakarta-regexp</artifactId> >> <version>1.4</version> >> <scope>runtime</scope> >> </dependency> >> >> It's not the only one, I've added several ones like that and they all >> appear in the resulting webapp WEB-INF/lib directory, except for this >> one. There is no exclude on jakarta-regexp in other dependencies, and >> I can't find what's wrong. Any idea? >> >> > >
