On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino wrote: > > There is no plans to upgrade Jetty. It implies some changes in > JettyLauncher and WebServer, I have already a patch for that but not > committed yet because I have not tested enough. If someone else demands it > we could consider to upgrade it. >
AFAIK, we can't update Jetty to 9.x because HTMLUnit (used for JUnitShell/GWTTestCase) depends on Jetty 8.x APIs (WebSockets) There's been a patch proposed already and it has been abandoned because of that. > Anyway I think it should be nice not to bundle jetty in the .jar deployed > in maven repos, but set it as a dependency so as it's easier to experiment > other versions. > It could possibly help with some setups but I doubt it'd be that useful. If we had a modularized GWT then you could avoid depending on gwt-junit, gwt-devmode-jettylauncher and gwt-codeserver (e.g. when compiling) and live with Jetty 9.x dependencies in your classpath/buildpath, or we could possibly provide a gwt-codeserver and/or gwt-devmode-jettylauncher using using Jetty 9.x; so you'd use Jetty 8.x with gwt-junit to run your unittests, and you could use Jetty 9.x in DevMode/superDevMode (and benefit from Jetty 9.x perf improvements for gwt-codeserver?) It's not possible with our current monolithic artifacts (and build) though. -- 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/d22e2d8b-0bf1-4f17-9805-9fdb944076f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
