HADOOP-18196. Remove replace-guava from replacer plugin#4152
Merged
tasanuma merged 1 commit intoapache:trunkfrom Apr 15, 2022
Merged
HADOOP-18196. Remove replace-guava from replacer plugin#4152tasanuma merged 1 commit intoapache:trunkfrom
tasanuma merged 1 commit intoapache:trunkfrom
Conversation
|
💔 -1 overall
This message was automatically generated. |
Contributor
Author
|
Thank you for the review @steveloughran. Could you please help merge this PR? |
Contributor
Author
Member
|
Thanks for finding the problem and fixing it, @virajjasani. Thanks for your review, @steveloughran. |
HarshitGupta11
pushed a commit
to HarshitGupta11/hadoop
that referenced
this pull request
Nov 28, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of PR
While running the build, realized that all replacer plugin executions run only after "banned-illegal-imports" enforcer plugin.
For instance,
Hence, if our source code uses com.google.common,
banned-illegal-importswill cause the build failure and replacer plugin would not even get executed.We should remove it as it is only redundant execution step.
How was this patch tested?
Local build
For code changes: