[CELEBORN-1616] Shade com.google.thirdparty to prevent dependency conflicts #2765
Conversation
This file contains 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
cxzl25
approved these changes
Sep 26, 2024
SteNicholas
approved these changes
Sep 26, 2024
FMX
approved these changes
Sep 27, 2024
HolyLow
pushed a commit
to HolyLow/celeborn
that referenced
this pull request
Oct 14, 2024
…flicts ### What changes were proposed in this pull request? shade `com.google.thirdparty` ### Why are the changes needed? prevent dependency conflicts ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? will let CI run Closes apache#2765 from akpatnam25/CELEBORN-1616. Authored-by: Aravind Patnam <[email protected]> Signed-off-by: mingji <[email protected]>
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.
What changes were proposed in this pull request?
shade
com.google.thirdpartyWhy are the changes needed?
prevent dependency conflicts
Does this PR introduce any user-facing change?
no
How was this patch tested?
will let CI run