I'd welcome a separate discussion about a backward compatibility contract,
but clearly we have to contrast the "technically Java 8 is supported" with
"realistically, any project that uses standard up-to-date tools can't use
Java 8 by the end of 2023". We support _end users_ to the extreme, as
My 2 cents:
We also have quite a few projects here based on GWT, still running DevMode
on Java 1.8 I am afraid.
Like everyone else sharing the same fate, we are struggling to upgrade to
Java 11 which seems to be the next sensible move.
Yet, the world is being indirectly and inevitably forced to
We have a project here that uses GWT for all its web UI and is still
running Java 1.8. The SAP JVM 8 will be supported at least until 2030.
According to
https://newrelic.com/resources/report/2022-state-of-java-ecosystem in April
2022 still close to half of the projects (46%) were using Java
I think first we should put a good Java version policy into place.
Personally I would split this policy into two policies. One for client code
(Compiler) and one for shared/server code.
For client code GWT has two main dependencies: Eclipse JDT and Jetty. So I
would define the minimum required