Hi there, I'm experiencing some very very strange behaviour in my project. The mvn compile goal is somehow generating/unpacking the following files into my target/classes directory:
javax/servlet/ServletRequest.class javax/servlet/RequestDispatcher.class javax/servlet/ServletContext.class javax/servlet/ServletResponse.class javax/servlet/ServletInputStream.class javax/servlet/ServletException.class javax/servlet/Servlet.class javax/servlet/ServletConfig.class javax/servlet/http/HttpServletRequest.class javax/servlet/http/Cookie.class javax/servlet/http/HttpSession.class javax/servlet/http/HttpSessionContext.class javax/servlet/http/HttpServletResponse.class javax/servlet/ServletOutputStream.class I'm at a loss as to how these are getting there. mvn --version provides: Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000) Java version: 1.6.0_11 Java home: /usr/local/java/jdk1.6.0_11/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.26.8-57.fc8" arch: "i386" Family: "unix" and the help:effective-pom informs me that I'm using version 2.0.2 of the maven-compiler-plugin. The classes copied into the target/classes directory look (but haven't been verified) like they're required for compilation to succeed. The behaviour is observed regardless of whether the servlet-api is expressed to be provided or compile, and whether the packaging is war or jar. Can someone shed some light on this please? It's causing Tomcat to fall over with a LinkageError on class-loading. Cheers Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
