Issue #8983 - Move multiple WebAppClassLoader implementations to common one in jetty-ee #12759
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.
Replacement for PR #12751 but more mindful of git rename (move) behavior, to retain history of moved classes from jetty-ee11 tree.
Create a
jetty-ee
WebAppClassLoader
that is used everywhere.Deprecate, gut, extend from jetty-ee version, but not remove, the older locations in the individual EE## locations.
The WebAppClassLoader specific tests have been moved to jetty-ee as well.