Hrm...
This looks like it could be a side effect from the package name change…
Different package, no dependency upgrade detected.
-Mike
On 8/10/22 07:50, Michael Conrad wrote:
I'm now using the following for GWT in our build.gradle files.
I've remove the gwtVersion from the gwt block and
I'm now using the following for GWT in our build.gradle files.
I've remove the gwtVersion from the gwt block and switched to using
gwtSdk to specify the GWT version.
Really not sure why it keeps getting overridden from dependencies, I
would have thought that pulling in gwt-dev would have
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:
||\---
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
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
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"
