What do you mean by "pure GWT frontend" ? Do you need servlets ? Or serving only static files would be OK? Because the problem is with server side code.
Le mar. 13 avr. 2021 à 21:01, Richi Plana <[email protected]> a écrit : > I should've been more explicit. The feature of having a self-contained app > server for pure gwt frontend development (for dev purposes). My > understanding is that it's a choice of bumping up Java version or losing > Jetty. > > On Tue., Apr. 13, 2021, 12:04 Thomas Broyer, <[email protected]> wrote: > >> 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 <[email protected]> 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 [email protected] >>> . >>> 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 [email protected] >>> . >>> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEOAgJFjDiacN7w31ASa3pg8bL%2B0mEOc1Q7Sy1cdCtTd4w%40mail.gmail.com >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEOAgJFjDiacN7w31ASa3pg8bL%2B0mEOc1Q7Sy1cdCtTd4w%40mail.gmail.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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAA5%3Digxoak0nwLOw%2B%3Dtyy0UXNpSaqp4_yL5DJsPM_4_jADEg4Q%40mail.gmail.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAA5%3Digxoak0nwLOw%2B%3Dtyy0UXNpSaqp4_yL5DJsPM_4_jADEg4Q%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEPYzJ49Ch11AFnREySWf%2BQKDEtCrw4jLy4iLzxnQ6fz-Q%40mail.gmail.com.
