chore: remove some unnecessary commons.lang3 usage - #8726
Merged
jeremylong merged 1 commit intoAug 10, 2026
Merged
Conversation
commons-lang3 often clashes with other plugins, especially in Gradle. Avoiding using it (or its deprecated methods) where possible. Signed-off-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com>
jeremylong
approved these changes
Aug 10, 2026
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 Change
commons-lang3 often clashes with other plugins, especially in Gradle since we dont isolate classpaths Avoiding using it (or its deprecated methods) where possible for these newer methods only added in more recent versions of commons-lang3, or with a clear alternative.
Would like to remove it more generally (and reduce its usage only to transitives) but will worry about that later.
Related issues
Have test cases been added to cover the new functionality?
yes