-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18022. Add restrict-imports-enforcer-rule for Guava Preconditions and remove remaining usages #3712
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
Conversation
…ons in hadoop-main pom
|
Could you please take a look @tasanuma? Thanks |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
JFYI @tasanuma, I am working on some test failures. Hopefully QA result tomorrow should be clean. |
|
Removed Preconditions usage from |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Recent test failures are not relevant. Timeline service issue is fixed with this PR. |
|
Thanks for working on this, @virajjasani. |
|
Thanks @tasanuma for the review.
Yeah indeed good question. Thanks to this incident that I realized that static imports are not caught unless explicitly mentioned so I have fixed pom for Preconditions static imports in the recent commit. As part of separate Jira, we can add static import tag for all other such banned imports. Sounds good? |
|
Thanks for fixing it. Sounds good. Please go ahead. |
|
+1, pending Jenkins. |
|
Thanks @tasanuma. Sure, once this PR is merged, will create another Jira and PR to include static imports for the classes we have added so far to avoid merge conflicts :) |
This comment has been minimized.
This comment has been minimized.
|
💔 -1 overall
This message was automatically generated. |
|
Done, finally only known and irrelevant test failures are present in the latest QA results. |
aajisaka
left a comment
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. Thank you @virajjasani and @tasanuma
|
Thanks for your contribution, @virajjasani. Thanks for your review, @aajisaka. |
…ons and remove remaining usages (apache#3712) Reviewed-by: Akira Ajisaka <aajisaka@apache.org> Signed-off-by: Takanobu Asanuma <tasanuma@apache.org>
Description of PR
Add restrict-imports-enforcer-rule for Guava Preconditions in hadoop-main pom to restrict any new import in future. Remove any remaining usages of Guava Preconditions from the codebase.
How was this patch tested?
Local testing.
For code changes: