As of somewhere in the time leading up to the GWT 2.9.0 release, it is no
longer possible to build GWT with Java7, and similarly the decision was
made to no longer officially support running on Java7
(jsinterop-annotations use of "TYPE_USE", newer jetty version too I
believe).
There is still
wrt running tests:
See https://gwt-review.googlesource.com/c/gwt/+/13861 for the pattern used
in JRE earlier; and the CI was updated to run in both 7 and 8 at the same
time.
PS: Compiler tests ("jjs.test.Java8Test") was different because we really
needed to run the compiler tests with new syntax i
I agree with this statement: "it seems like the clearest win is to move all
the way to Java11, though continue to target java 8 releases, and test on
all JREs up until current."
On Mon, Jun 29, 2020 at 10:21 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.c
Right - the excludes via ant are certainly an option ("use ant filters"), my
main hope is to avoid adding another stanza of xml for the emulation for each
release. Cutting out Java7 and adding a "java 11 or higher" to lump all the
java 9, 10, 11 tests in would at least be a net equal in XML from
I was clarifying what I was expecting the setup to look like wrt different
versions supported.
I agree that the granularity of the supported version doesn't need to be
lower than what is useful to us (which I think is driven by both LTS and
also by GWT releases).
On Mon, Jun 29, 2020 at 7:47 PM Co