super dev mode Jetty version?

[Edward Scott]

My project has transitive dependencies on log4j-api and log4j-core and
normally pulls in 2.9.1, but when I run in super dev mode this leads to
a RuntimeException scanning ProcessIdUtil.class similar to what is reported
here
<https://stackoverflow.com/questions/46878035/error-scanning-entry-meta-inf-versions-9-org-apache-logging-log4j-util-stackloca>.
Following through to the Jetty github issue
<https://github.com/eclipse/jetty.project/issues/1797> shows the issue was
resolved in Jetty 9.3.x and 9.4.x. GWT super dev mode meanwhile is using
Jetty 9.2.14.

Several ideas I am exploring -

- Is it possible to configure my project to use Jetty 9.3.x in super dev
mode?
- Is there any upcoming update to GWT what would update the Jetty
version?
- Is it possible to configure my project to use one version of the log4j
dependencies in super dev mode but use another in the deployed artifact?

Any suggestions or ideas would be most welcome.

[Jens]

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.

[p***@yale.edu]

Hi Jens,
I have a similar issue to what Edward described but with Elasticsearch
versions above 6.1.1.
Could you please help to reduce the "minimal amount of time to install my
own Jetty" by providing some guidance on how to accomplish that. The
documentation is not particularly clear on how to do that. I am using
IntelliJ.
Hope you can help.
Thanks,
Peter

PS It would be great not to deal with that issue at all and have an
up-to-date version of Jetty as was the case for many years of working with
GWT without all these troubles. Switching to SuperDev mode and losing the
ability to debug directly in IntelliJ was a huge step back and now that.
GWT is an amazing under-appreciated API but little effort is made lately to
make it better and help developers to focus on development rather than
configuration incompatibilities.

Post by Jens
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.