tomcatRun doesn't do anything about gradle-tomcat-plugin HOT 6 CLOSED

This is the same issue as #14.

from gradle-tomcat-plugin.

Not sure if it is exact the same, as tomcatRun seems to deploy at least something in that case in our case it does nothing. tomcatRunWar seems to deploy the application (judging from the log output) but basically makes the application unreachable.

We are basically stuck here, as Jetty isn't capable of Servlet 3.0 (at least not with the plugin). The cargo plugin seems to require a pre-installed server to be able to deploy to and this one doesn't deploy properly. So basically gradle and servlet 3.0 and automated testing/deployment seems a lost cause for now (at least without having to write your own script to do deployment/undeployment).

from gradle-tomcat-plugin.

I will need to have a deeper look at the Servlet 3.0 support again as more and more people start to use it. Thanks for reporting it. I will try to attack this next week.

from gradle-tomcat-plugin.

If you need anything feel free to contact me. Is there anything special in the plugin that prevents the normal behavior or maybe the embedded tomcat instead of the full tomcat?

from gradle-tomcat-plugin.

Cool, thanks! Do you have a sample project I can use to debug this issue? At least tomcatRun refers to web.xml implicitly.

from gradle-tomcat-plugin.

This is fixed with version 0.9.2.

from gradle-tomcat-plugin.