SV: dependency quirck?
This is strange. Test it some more and be sure you do it correct and if you are doing everything the right way you should file it as a bug in jira. You can also try scope = system. This is what the documentation says: PROVIDED - this is much like compile, but indicates you expect the JDK or a container to provide it. It is only available on the compilation classpath, and is not transitive. -Ronny -Opprinnelig melding- Fra: Jeroen Verhagen [mailto:[EMAIL PROTECTED] Sendt: 9. oktober 2006 13:56 Til: Maven Users List Emne: Re: dependency quirck? Hi Ronny, On 10/9/06, Naess, Ronny <[EMAIL PROTECTED]> wrote: > Compile scope is included in classpath. Try scope = provided I tried that, made sure everything was cleaned but the servlet-api jar is still there. regards, Jeroen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:452a38fa322741367111490! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SV: dependency quirck?
Compile scope is included in classpath. Try scope = provided More on scopes http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html -Ronny -Opprinnelig melding- Fra: Jeroen Verhagen [mailto:[EMAIL PROTECTED] Sendt: 9. oktober 2006 13:22 Til: users@maven.apache.org Emne: 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 (compile). 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\ser vlet-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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:452a30ed225875315134984! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
