Update log4j2 LICENSE and NOTICE files #93611
Merged
Conversation
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
joegallo
added
>non-issue
:Delivery/Build
Collaborator
|
Pinging @elastic/es-delivery (Team:Delivery) |
pugnascotia
approved these changes
Feb 9, 2023
joegallo
added a commit
that referenced
this pull request
Feb 9, 2023
joegallo
added a commit
that referenced
this pull request
Feb 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I noticed that the LICENSE.txt and NOTICE.txt that we have for many of our log4j dependencies are out of date.
I'm using the files from the top-level of https://github.com/apache/logging-log4j2 for this update.
You could also compare against the most recent download (https://logging.apache.org/log4j/2.x/download.html) -- that one has an out of date copyright year in the NOTICE, though, which is is why I'm sticking with the ones from git directly (see apache/logging-log4j2@0c01699).