That only seems to work at random! For some strange reason 3 out of 5 builds are correct when the scope is set, but those other 2 builds still have the JAR! I have no problem with building a couple of times more, but for automated testing this is disastrous!
Roland On Monday 29 May 2006 15:09, Kees de Kooter wrote: > Give it scope "provided". > > On 5/29/06, Roland Asmann <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am building a WAR, in which I would like to remove some JAR's that come > > up transitively. I've tried to configure my war-plugin like this: > > > > <plugin> > > <artifactId>maven-war-plugin</artifactId> > > <configuration> > > <archive> > > <compress>false</compress> > > <manifest> > > <addClasspath>true</addClasspath> > > </manifest> > > </archive> > > > > <dependentWarExcludes>commons-logging</dependentWarExcludes> > > </configuration> > > </plugin> > > > > But this doesn't seem to work. Could anybody tell me how to exclude > > commons-logging from the WAR? And also, could someone explain what this > > 'dependentWarExcludes' does?? > > > > Thanks, > > > > Roland > > > > > > --------------------------------------------------------------------- > > 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]
