Upgrade Servlet API to 3.1.0 #806
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Something to keep in mind is that those of us using Google App Engine are still stuck on servlet 2.5 for feature support in production. |
Member
|
It should be alright now to upgrade though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running SuperDevMode for a GWTP app using GWT 2.8.0-rc1 throws a
java.lang.NoSuchMethodErrordue to conflicting Servlet APIs: The Jetty web server bundled with 2.8.0-rc1 depends on 3.1.0 whereas GWTP still uses 2.5.0 (see also https://groups.google.com/d/msg/google-web-toolkit/S9KV1GaCyvg/N9GsmoWvAQAJ).This PR upgrades the Servlet API to 3.1.0. Running a quick
mvn clean installdid not show any problems in using 3.1.0