HADOOP-17971. Exclude IBM Java security classes from being shaded/relocated.#3567
Merged
aajisaka merged 3 commits intoapache:trunkfrom Oct 20, 2021
Merged
Conversation
|
💔 -1 overall
This message was automatically generated. |
HarshitGupta11
pushed a commit
to HarshitGupta11/hadoop
that referenced
this pull request
Nov 28, 2022
…ocated. (apache#3567) Signed-off-by: Akira Ajisaka <aajisaka@apache.org>
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
Exclude IBM Java security classes located in com.ibm.security* from being shaded.
How was this patch tested?
Manual injection of UserGroupInformation class files (which contain references to com.ibm.security classes) that were compiled manually.
I followed bug fixes for similar issues. IBM java isn't actually used in source code except being referenced when it is the running JVM.