@eliasbalasis: Why you need 5 steps to run the application in a GWT multi module project? I have two runnning configuration, one for the code server another for the server. I, personally, prefer Spring boot. Starts very fast! And, if you running your app in the cloud, Spring Boot is awesome.
t.br...@gmail.com schrieb am Dienstag, 13. April 2021 um 20:04:04 UTC+2: > Which features are you talking about? Which would you lose by switching to > using a *real* Jetty server alongside GWT CodeServer? > > Le mar. 13 avr. 2021 à 20:01, Richi Plana <ric...@gmail.com> a écrit : > >> As a user and non-contributor, I would vote for bumping up versions (Java >> 7 to 8, Jetty to 9.4). The move to Java 8 is something I would have to do >> if I had any Java 7 projects left. And Jetty has lots of used features that >> I'm not hearing proposals for replacement for. >> On 2021-04-11 9:15 a.m., Jens wrote: >> >> Hi, >> >> we all know the issue: DevMode bundles Jetty and people are using it even >> though we do not recommend it. Consequently people are complaining that >> bundled Jetty is too old. So every once in a while we upgrade it. >> >> Currently with GWT 2.9.0 the situation is: >> - GWT SDK is compiled to Java 7 byte code >> - GWT Compiler requires ASM 7.x to support Java 11 >> - DevMode bundles Jetty 9.2 which uses ASM 5.x >> - gwt-dev.jar can only bundle a single Jetty, since we do not relocate >> it. However there is already a question asking for Jakarta Servlet support, >> e.g. Jetty 11 / Tomcat 10. >> >> Currently the ASM version misalignment between Jetty 9.2 and GWT compiler >> causes classpath issues. This could be fixed by upgrading to Jetty 9.4 and >> consequently compiling GWT SDK to Java 8 byte code as that is a requirement >> for Jetty 9.4. >> >> However given the new Jakarta namespace and first questions about >> supporting it, I am wondering if it wouldn't be wiser to remove embedded >> Jetty from DevMode now, invest some work to make GWT-RPC and RequestFactory >> useable with old javax.servlet and new jakarta.servlet namespaces and >> finally cut a 2.10 or 3.0 release given the removal of embedded Jetty. >> >> Personally I would strongly vote for removal because GWT nowadays is in >> maintenance mode with only very few changes here and there to support J2CL >> better. Even reviews from contributors are rare these days I guess. Every >> action we take nowadays should take maintenance effort into account and a >> low maintenance effort is obviously preferred. If we upgrade Jetty to 9.4 >> we still have that Jakarta issue coming up more often in the future for >> sure. >> >> Generally this would be a decision made by GWT steering group but I have >> no idea if this group still exists. So I am asking here for a decision how >> to move on. >> >> -- J. >> -- >> 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 google-web-toolkit-co...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/622544a8-85d5-41c5-b8da-7a733667eb89n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/622544a8-85d5-41c5-b8da-7a733667eb89n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> 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 google-web-toolkit-co...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/c317be1c-55d9-f255-0b0f-e05da19240ee%40gmail.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/c317be1c-55d9-f255-0b0f-e05da19240ee%40gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/2fb3b18a-506e-4c24-b59c-bd279aa62e12n%40googlegroups.com.
