The easiest solution would be to invest a minimal amount of time to install and configure your own Jetty server and use it instead of the embedded Jetty provided by GWT. This has the big benefit that you can configure anything you like and match your production environment without any GWT stuff involved.
GWT might update its internal Jetty not just because of its dependencies but also because it doesn't work with web app libraries containing module-info.clas files (Java 9), see https://github.com/gwtproject/gwt/issues/9606 . However it is not a high priority given you can always use your own server, which is actually the recommend solution. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
