feat(logging): #13378 Uniformly uses log4j2 as the logging component #13402
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.
What is the purpose of the change
Currently in Dubbo, there is a mixed use of log components, and some modules lack log configuration, due to no log output. Therefore, uniformly use log4j2 can reduce the learning and cost, reduce logging component conflicts
Brief changelog
Replace log4j and logback with log4j2, providing a simple Log4j2 configuration. Unfortunately log4j2 does not support native, so have to use logback, update future while log4j2 support native.
Adjusted versions of some artifacts in pom.xml to unify them as much as possible to the BOM.
Verifying this change
ci passed
Checklist