Wendy is right. Provided scope is not the solution. /Anders
On Mon, Jan 17, 2011 at 14:46, Wendy Smoak <[email protected]> wrote: > On Mon, Jan 17, 2011 at 7:59 AM, Jesse Farinacci <[email protected]> wrote: > > > The scope=provided instructs Maven to not actually bring that > > dependency into the classpath, thus, it behaves as a global exclude. > > My understanding of 'provided' is that it *does* go on the classpath > for compilation, but it is not transitive (and does not get packaged). > > The typical use is for the Servlet API in your .war file -- you need > it to compile, but you don't want it in WEB-INF/lib because the > container will provide it. > > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
