Java11 support

[Alexander Leshkin]

Is there any one who works on Java 11 support? I mean updating dependencies and new "sourceLevel" introduction.

If not and if there is an interest in this, I can try to create PR.

[Hristo Stoyanov]

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?

[Colin Alworth]

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 review if you're interested in those things as well.

We're still here, but almost all of this work is done in our free time - if you have something you'd like to see done more quickly, please do watch reviews, help by making comments to improve the code and get it landed more quickly, and consider authoring some changes or directly supporting the developers who are authoring them.

[Hristo Stoyanov]

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: downstream projects, such as Errai won't move to Java 11 unless there is an official GWT release for it.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Contributors" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit-contributors/JEhmxkH-xOQ/unsubscribe.
To unsubscribe from this group and all its topics, 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/3da4b019-31df-4c32-a53a-9077ad2696f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

/ Hristo Stoyanov

[Jens]

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: downstream projects, such as Errai won't move to Java 11 unless there is an official GWT release for it.

GWT depends on Eclipse JDT, and the current stable version used in https://gwt-review.googlesource.com/c/gwt/+/21540 is missing some valuable bugfixes that will be part of the next JDT 4.11 release (will be released when Eclipse 2019-03 will be released). One of the main features of Java 11 is using the var keyword in lambda parameters. However that fails for Function and Predicate with the current JDT release but has been fixed for the next release. There is also a compilation slowdown fixed.

So I think it is better to wait for JDT 4.11 in march and use the time to review Colins JRE emulation (which you can also help reviewing), making the GWT ant build Java 11 compatible and update the CI build of GWT to use Java 11 (with -release 1.8 or course).

-- J.

[krypto...@gmail.com]

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).

[ign...@bacamt.com]

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.