Skip to content
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

Upgrade log4j to 2.16.0 #101

Closed
wants to merge 1 commit into from
Closed

Upgrade log4j to 2.16.0 #101

wants to merge 1 commit into from

Conversation

sruti1312
Copy link
Contributor

@sruti1312 sruti1312 commented Dec 14, 2021

Signed-off-by: Sruti Parthiban partsrut@amazon.com

Is your feature request related to a problem? Please provide an existing Issue # , or describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you are proposing
Upgrade log4j to 2.16.0

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Check List

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Sruti Parthiban <partsrut@amazon.com>
@sruti1312 sruti1312 requested a review from a team December 14, 2021 20:36
@dblock
Copy link
Member

dblock commented Dec 21, 2021

Superseded with 2.17 upgrades.

@dblock dblock closed this Dec 21, 2021
@sruti1312 sruti1312 deleted the feature/upgrade-log4j branch January 21, 2022 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants