Meh,
I've managed to break my GWT setup again. This time for superdev mode.
Looking for suggestions on where the (I assume) Jetty conflict is coming
from.
Getting the following stacktrace after "Module setup completed" is
logged when trying to run "./gradlew subproject:gwtSuperDev"
Thanks for the assistance.
After poking around a bit, I removed the dependency and switched to using
Element2 for websock work.
On Fri, Aug 5, 2022 at 11:41 AM Jens wrote:
> GWT (gwt-dev) depends on ASM 9.2 which supports up to Java 18. On your
> compile classpath you have gwt-websockets which
When running unit tests, I receive the following error.
java.lang.IncompatibleClassChangeError: Type
com.google.gwt.dom.client.Style$Overflow$1 is not a nest member of
com.google.gwt.dom.client.Style: current type is not listed as a nest member
Any insight will be greatly appreciated.
--
You
Your stack trace lines up except for the top frame - jetty-io
9.4.4.v20210927 has a blank line for SelectorManager.java:81, and the
source for the file at that version doesn't contain the string "No
selectors". On the other hand, jetty-io 9.2.14.v20151116 has this as a
constructor (and line 81
So, I'm guessing that gretty jetty is leaking into gwt super dev mode
somehow.
I added the following as a compile time dependency, and superdev mode
seems to be working.
providedCompile"net.sourceforge.htmlunit:htmlunit:2.55.0" // to get superdev
mode working
On 8/9/22 10:20, Michael
My apologies, I didn't notice your attachment until I had already hit send.
Checking the list shows that gwt-materialdesign is bringing in an old
version of htmlunit (GWT 2.10.0 updated this also), which is in turn
bringing in some old jetty versions:
||\---
