I've not looked at the code, but I'll chime in my support for Manuel's approach--I think the JettyLauncher/SuperDevMode class would be the easiest transition path for us.
(Not all of our devs use GPE, so while the facets sound spiffy/etc., hopefully they would be an alternative and not a replacement.) Goktug's idea of shipping servlets is pretty intriguing, in terms of getting Jetty out of GWT core all together; I think the only complexity would be conditionally mangling the web.xml for dev vs. prod mode (e.g. I assume we wouldn't want the proposed GWT SuperDevMode servlet in the web.xml that is deployed to production). - Stephen -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/20140702120425.7e5b82ae%40sh9. For more options, visit https://groups.google.com/d/optout.
