-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed startup of context c.g.g.d.s.j.WebAppContextWithReload #2192
Comments
This is related to your use of a JEP-238 Multi-Release JAR. Notice the path ..
Issue #1797 is where this was first reported and fixed.
Since Jetty 9.2.x is end of life, there will be no backport to support JEP-238 on Jetty 9.2.x. Your choices are to upgrade to one of the supported versions listed above, or downgrade your version of log4j to one that does not use JEP-238 Multi-Release JAR Files. |
Also of note, the log4j JEP-238 Multi-Release JAR file you are using is also a Java 9 JPMS module. The presence |
How can I force GWT 2.8.2 to use Jetty 9.4.x? I just tried to update the dependencies manually, but really, I landed in dependency hell and gave up. |
@diskostu you might want to update to GWT 2.9.0 See: https://groups.google.com/forum/#!topic/google-web-toolkit/kXWfvW9X0pI It's available on Maven Central as well - https://search.maven.org/artifact/com.google.gwt/gwt/2.9.0/pom |
Hi:
I need help with an issue I have no idea how to resolve. Your help will be greatly appreciated.
I just added log4j2 jars (log4j-api-2.10.0.jar, log4j-core-2.10.0.jar) to my Web app and it started running into this problem in my dev. Later I added log4j-web-2.10.0.jar and tried, it still fails with the same message.
Here's my environment:
Stack trace (partial):
The text was updated successfully, but these errors were encountered: