OK, great. The embedded Tomcat implementation requires you to put slightly different JAR files into your classpath than the full-blown Tomcat installation. Think of it as a minimalistic version of a Tomcat installation. You also have to consider transitive dependencies that you declare in your classpath. I might add a "tomcat" configuration in a future version of the plugin which makes it easier to log Tomcat's classpath for people to see what exactly was added.
In general you would have to compare the libraries in tomcat/lib. That's correct. The only issues I think you'll run into are with the Servlet and JSP libraries. I'll also add this as a FAQ in the plugin's readme file. -- View this message in context: http://gradle.1045684.n5.nabble.com/Strange-classpath-issue-when-starting-tomcat-7-programmatically-tp4288368p4387248.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
