-
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
Addendum to #11566. #11722
Addendum to #11566. #11722
Conversation
Restored methods that were removed in WebAppClassLoader.Context. Fixed method signatures for deprecated method -- they must take the deprecated ClassMatcher, not the newly introduced one. Signed-off-by: Simone Bordet <[email protected]>
Test failures, all in ee8 layer |
Signed-off-by: Simone Bordet <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the work in core/EE10, but I think we should leave EE8/EE9 as much as possible with the old naming in the APIs and just use the new names in the implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The intention was to not do the public API renaming in EE8/EE9 APIs. i.e. leave as system/server rather than change to protected/hidden. The new vocab will appear to some extent in ClassMatchers returned from the APIs, but there is no need to add it to the EE8/EE9 APIs if they were not already there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
I have un-deprecated ee9's ClassMatcher
because it is used in every non-deprecated APIs (since ee9 does not have the new APIs, the old APIs cannot be deprecated, and so ee9's ClassMatcher
should also not deprecated).
Signed-off-by: Simone Bordet <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Re-running CI to see if the failures are flakes.
This is still broken.
|
Thanks, on it. |
Signed-off-by: Simone Bordet <[email protected]>
#11566
Restored methods that were removed in WebAppClassLoader.Context.
Fixed method signatures for deprecated method -- they must take the deprecated ClassMatcher, not the newly introduced one.