Provided means that it will be provided by the container (e.g. think Servlet API jar). Maven will provide it on the compile and test classpaths.
You would not want the servlet API that you are using for compile time into the Tomcat classpath as tomcat is providing that dependency for you. There are all sorts of classloader issues that would arrise. What you need to do is to explicitly tell the tomcat-maven-plugin what dependencies in, addition to the standard dependencies, to make available to the tomcat conatiner it makes available to you. I'm not sure exactly how you do this with the tomcat plugin, but I would expect it to be by adding dependencies to the plugin configuration. On Dec 14, 2007 2:31 PM, Alexandre Gomes <[EMAIL PROTECTED]> wrote: > I'm not sure if I found a bug in tomcat-maven-plugin or if it's an expected > behaviour [1]. > > 1) Create a project with a "provided" scoped dependency [2] > 2) Try to execute tomcat:deploy with -DperformRelease=true [3] > 3) During the javadoc:jar phase, a warning is raised [4] > > [1] > > http://mojo.codehaus.org/tomcat-maven-plugin > > [2] > > <dependency> > <groupId>xstream</groupId> > <artifactId>xstream</artifactId> > <version>1.0.1</version> > <scope>provided</scope> > <type>jar</type> > </dependency> > > [3] > > mvn tomcat:deploy > -Dmaven.tomcat.url=http://192.168.1.40:8080/manager-DperformRelease=true > > [4] > > [INFO] Javadoc Warnings > [WARNING] > /Users/alegomes/Documents/tmp/seaup.sea/src/main/java/br/com/seatecnologia/seaup/negocio/ConvertendoXML.java:5: > package com.thoughtworks.xstream does not exist > [WARNING] import com.thoughtworks.xstream.XStream; > [WARNING] ^ > [INFO] Building jar: /Users/alegomes/Documents/tmp/seaup.sea/target/seaup- > javadoc.jar > > > thanks > Alexandre Gomes > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
