Could it be that you build once without scope provided and so the jar resides in your target directory? Try a mvn clean install to see if that clears the problem.
If that doesn't work take a look at the output of mvn dependency:tree to see where it comes from. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 8, 2009 at 11:44 PM, John A Pershing Jr <[email protected]>wrote: > Pardon my ignorance, but I'm trying to wade through / debug the Hibernate > tutorial, and it more-or-less requires the use of Maven to build and package > the example applications. I have only figured out enough about Maven to be > dangerous. > > From reading the documentation, it sounds like the dependency: > > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > <version>2.5</version> > <scope>provided</scope> > </dependency> > > should make the 'servlet-api' jar available at compile time, but *not* > package it up into the resulting war file. However, it *is* including this > jar in the output war file, which causes Apache to complain. > > Do I need some other clause in my pom.xml file to tell Maven that (1) the > jar really is provided by the runtime, so that (2) I don't want it included > in the packaged war file? > > -jp > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
