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 
Following through to the Jetty github issue 
<> 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 
   - Is there any upcoming update to GWT what would update the Jetty 
   - 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.

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 post to this group, send email to
Visit this group at
For more options, visit

Reply via email to