-
Notifications
You must be signed in to change notification settings - Fork 82
Update log4j to 2.17.1 #644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Also, move classes using log4j to slf4j. Signed-off-by: Taylor Smock <[email protected]>
Signed-off-by: Taylor Smock <[email protected]>
|
Note: We can use dependency substitution to use the osgeo -norce version instead of excluding osgeo. |
Bentleysb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great. Thanks for working to update this. Have you done any test runs with these changes, local or remote?
|
log4j 2.16.0 creates another vulnerability (CVE-2021-45105). So we need to upgrade to 2.17.0. Edit - now we need it updated to 2.17.1 |
Also update Jacoco, Junit, and SQLite, all of which should have no source compatibility issues. Signed-off-by: Taylor Smock <[email protected]>
|
Kudos, SonarCloud Quality Gate passed! |
I have done a local run with some additional dependency updates ( |
|
I took tsmock's branch and executed on AWS EMR and it looked like it was working correctly. |








Also, move classes using log4j to slf4j.
This should have no effect on runtime logging.
See also