Affects Version/s: 1.1
Fix Version/s: backlog
Thanks for a great Maven plugin in tomcat-maven-plugin. I am using it in my Open Source project and it works really well.
I recently tried getting tomcat-maven-plugin to coexist with jetty-maven-plugin. There is a problem that appears to sit somewhere in the middle of the two projects, and requires both of you to agree on a solution
Basically tomcat-maven-plugin appears to be setting INITIAL_CONTEXT at the VM level (whereas Jetty does not) and this means that Jetty ends up trying to use Tomcat's JNDI implementation. It would be great if Tomcat/Jetty could live together in a build process, so that I could run my integration tests against multiple appservers.
Please see JETTY-1370 for an example pom.xml and an error log, and also discussion from the jetty-maven-plugin guys about what might be 'wrong'.