[INLONG-8753][Audit] Separate commons-text from org.apache.flume #8754
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
dockerzhang
approved these changes
Aug 17, 2023
aloyszhang
approved these changes
Aug 17, 2023
liaosunny123
pushed a commit
to liaosunny123/inlong
that referenced
this pull request
Oct 11, 2023
…che#8754) * Separate commons-text from org.apache.flume * update commons-text version
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.
Prepare a Pull Request
Motivation
Separate commons-text from org.apache.flume, because flume uses the old version of commons-text, there will be security issues
Modifications
Separate commons-text from org.apache.flume.