GWT has a hard dependency on JDT so I see it pragmatic and I would let GWT require to what JDT requires in order to support the latest Java language features. And for that version the latest Jetty server can be chosen.
Given that GWT is in maintenance mode GWTs server libraries can stay at 8 as long as feasable because there is no real benefit updating the requirement. But for running GWT compiler / DevMode I really don't mind which Java version is required and I don't see any reason why GWT needs to be extra conservative here. It is just the VM to run a tool and has nothing to do with the final deployment. -- J. Colin Alworth schrieb am Sonntag, 26. Oktober 2025 um 20:28:58 UTC+1: > Its been about three years since the last thread on deprecations, and the > Java 8 deprecation ended up going by with barely a whisper. > > On the other hand, I'm hearing more interest in Java 21+ features than we > did for Java 17 at the time - but updating JDT so that we can provide those > will require dropping support to run on Java 11. > > We seem to be close to a GWT 2.13 release, so GWT 2.14 would be the > earliest this would take place. The expectation in turn would be that our > JDT version would then be updated, and possibly Jetty as well. Thoughts? > -- 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 visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a4ac10bd-cd59-4000-9fbc-9dfab7cf9224n%40googlegroups.com.
