You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jeroen Verhagen <je...@gmail.com> on 2006/10/09 13:21:50 UTC
dependency quirck?
Hi all,
I'm having a problem a with servlet-api jar being deployed even though
its scope is set to compile.
I'm exploring mvn by creating a webapplication that is divided into
two modules. A core module generating a jar and containing servlets,
Spring controlllers. A web module contains the jsp's, web.xml etc.
This is the way, right?
The core module has a dependency on the servlet-api jar for
compilation (<scope>compile</scope>). The web module has a ofcourse a
dependency on the core module. However the problem is that when the
web module is deployed (war and exploded dir) the servlet-api is also
deployed, eventhough it's scope in the core pom is set to compile.
What's causing this? It's a problem because I think the deployment on
Tomcat takes longer and it complains about an offending class:
INFO: validateJarFile(C:\java\jakarta-tomcat-5.5.9\webapps\web\WEB-INF\lib\servlet-api-2.4.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending
class: javax/servlet/Servlet.class
Thanks for any help,
Jeroen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org