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
Totally agree with everything said above
On Thursday, April 25, 2019 at 12:31:36 PM UTC-4, t.b...@gmail.com wrote:
>
> Hi all,
>
> 3½ years ago, we announced 2.8.0-beta1 and that it now required JDK 7, and
> that started quite a long discussion:
> https://groups.google.com/d/topic/google-web-to
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
I am totally fine with requiring JDK 8 when using GWT.
Personally I would even like to see requiring at minimum the Java version
we provide emulation for. That would free us from super sourcing emulation
tests for newer Java APIs / syntax which is quite annoying. Also your ANT
build could requ
All makes perfect sense to me. I don't really see any pluses of failing to
support some people who are helping push gwt forward just so it continues to
work with an outdated jdk.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscri
Hi all,
3½ years ago, we announced 2.8.0-beta1 and that it now required JDK 7, and
that started quite a long discussion:
https://groups.google.com/d/topic/google-web-toolkit-contributors/TzsINiDf5xg/discussion
A few days ago, there's been renewed interest into upgrading the Jetty
version GWT is