We are using GWT HEAD-SNAPSHOT in production with Java 11, both target and
JDK, in a project using RxJava and AutoREST so looks like the bug was fixed
and included in 3.17 JDT release which is the one added to GWT.
On Thursday, April 25, 2019 at 8:49:23 PM UTC+2, krypto...@gmail.com wrote:
>
> T
This bug in the JDT compiler is worth noting. I ran into last summer when
trying to upgrade the JDT to handle newer versions of java inside of GWT:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=538126
It affects RXJava/GWT-Autorest and is scheduled to be fixed in 4.12 (very
tentatively).
On Th
> Colin,
> My concern is that a lot of time is spent on re-writing RPC, XML
> UI-binding. Given how short-handed the maintainers are, should we not focus
> on just one thing - 2.9 with basic compiler support for Java 11 jdk? I
> don't even advocate for porting any new core Java 9+ JDK APIs.
Colin,
My concern is that a lot of time is spent on re-writing RPC, XML
UI-binding. Given how short-handed the maintainers are, should we not focus
on just one thing - 2.9 with basic compiler support for Java 11 jdk? I
don't even advocate for porting any new core Java 9+ JDK APIs.
... Even worse:
Alexander has patches up for Java 11 language support - if we ship now, we
won't be compatible with Java 11 (unless you just mean running the compiler
on a Java 11 JDK, but as I understand it, we're already good there with
2.8.2?).
I have patches up for Java 9, 10 JRE support, which also need r
I am also curious. GWT 2.8.2 being on Java 8 is major holdup for my
projects. Whatever happened to the GWT steering committee ??? Can we just
get GWT 2.9 with the only feature being Java 11 support?
On Monday, January 7, 2019 at 10:19:28 AM UTC-8, Alexander Leshkin wrote:
>
> Is there any one w
