I have a maven project that depends on the servlet-api jar. For some reason, in the compile phase, it's putting the javax.servlet.* classes into target/classes. That is, after "mvn process-resources", target/classes/javax doesn't exist, but after "mvn compile", it does. There is no "javax" package in the source directory. I've found two ways to make it not do this:
1) Remove the explicit dependency on the servlet jar. This works even though the compilation dependency on servlet-api is still fulfilled by a transitive dependency from another library. 2) Delete most of the code from the source directory and compile only a couple of classes. I haven't been able to narrow it down much further than this yet. I'm just completely baffled by this, and I wanted to see if anyone had heard of anything like this before. I've tried it with maven 2.2.1 on Ubuntu 9.10 and Windows 7, and I've also tried maven 2.0.10 on Ubuntu, all with the same result. -- View this message in context: http://old.nabble.com/Maven-compile-puts-javax.servlet.*-in-target-classes-tp27135933p27135933.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
