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. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
