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
Plugins: Remove support for onModule #21416
Conversation
All plugin extension points have been converted to pull based interfaces. This change removes the infrastructure for the black-magic onModule methods.
w00t. Do we need breaking java changes in the docs? |
Yes. |
Regarding the breaking changes, since this will go back to 5.1, should it just go into the backport since there are no 5.1 breaking changes in master? |
That's exactly how I handle these sorts of things. |
hell yeah! |
retest this please |
@nik9000 @jasontedor @s1monw Do you have any technical comments on this PR or is it just needing the breaking changes docs when backported? |
Just that, the PR looks good to me. I'll leave a formal LGTM. |
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.
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.
Same here. Change looks fine.
All plugin extension points have been converted to pull based interfaces. This change removes the infrastructure for the black-magic onModule methods.
With the backport to 5.x, I pushed 2162a6d with a breaking changes note. /cc @clintongormley |
thanks @rjernst |
All plugin extension points have been converted to pull based
interfaces. This change removes the infrastructure for the black-magic
onModule methods.