[MINOR] Upgrade log4j version to 2.17.0 #662
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
…to maven repository
… into develop � Conflicts: � build.gradle � eventmesh-common/build.gradle � eventmesh-connector-api/build.gradle � eventmesh-runtime/build.gradle � gradle.properties
* fix: dist task exception
* Add files via upload * Update README.md * [ISSUE apache#580] Add checkstyle gradle plugin (apache#581) * Add checkstyle gradle plugin, change plugin package * skip check in ci * update wechat-official qr code * update mesh-helper qr code * Add files via upload * update README.md * update README.md * Update .asf.yaml * [ISSUE apache#588] Fix typo in README.md (apache#589) close apache#588 * [Bug apache#590] Consumer subscription topic is invalid (apache#590) (apache#592) * [Bug apache#590] Consumer subscription topic is invalid (apache#590) * [Bug apache#590] Consumer subscription topic is invalid (apache#590) close apache#590 * fixed a wrong url in cn-doc (apache#585) close apache#596 * resolve_exception->Consumer subscription topic is invalid apache#590 (apache#598) close apache#590 * Update eventmesh-store-quickstart.md * Update README.md * Add slack icon (apache#601) * eventmesh-admin-rocketmq submodule and createTopic REST API (apache#530) * eventmesh-admin-rocketmq submodule and createTopic draft API * add license header * change to /topicmanage * fix build error * fix some code check style issues close apache#435 apache#346 * create topic command (apache#531) * create topic command * address review comments * fix build and add createtopic method to standalone module * fix build issue * fix a few remaining code check issues * fix test close apache#346 * Update README.md * Safely delete useless log4j dependencies * Safely delete outdated metrics dependencies * Sately delete useless collections4 dependency * Safely delete useless commons dependencies * Reback to the collections4, but let it not in api dependency * Could not remove text for Safe Ramdom implementation * Fix build error * Add collection4 * Fix build error * Revert "Safely delete outdated metrics dependencies" This reverts commit 92287b0. * Change to api dependency * Remove doclint warnings * Depracated checkstyle check error temporarily, we should remove it when we polish later * Update .asf.yaml * Update .asf.yaml Co-authored-by: Eason Chen <[email protected]> Co-authored-by: Wenjun Ruan <[email protected]> Co-authored-by: Nicholas Zhan <[email protected]> Co-authored-by: hagsyn <[email protected]> Co-authored-by: sarihuangshanrong <[email protected]> Co-authored-by: yuri <[email protected]> Co-authored-by: vongosling <[email protected]>
xwm1992
added a commit
to xwm1992/EventMesh
that referenced
this pull request
Dec 27, 2021
* Update log4j version * update log4j known-dependencies.txt
xwm1992
added a commit
that referenced
this pull request
Aug 4, 2022
* Update log4j version * update log4j known-dependencies.txt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since log4j2 2.17.0 has been released, and it solved some security issue, we need to upgrade log4j version before 1.3.0 release.
More detail can see https://logging.apache.org/log4j/2.x/security.html.