-
Notifications
You must be signed in to change notification settings - Fork 11.5k
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
[ISSUE #5484] Replace Logging Module with Shaded Logback #5524
Conversation
ee8f2cd
to
c471b61
Compare
b99bacb
to
d34961a
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5524 +/- ##
=============================================
- Coverage 42.65% 42.41% -0.24%
+ Complexity 8013 7933 -80
=============================================
Files 1031 1020 -11
Lines 72735 71142 -1593
Branches 9610 9380 -230
=============================================
- Hits 31022 30172 -850
+ Misses 37772 37153 -619
+ Partials 3941 3817 -124
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
d34961a
to
e95a22e
Compare
1bbf9f3
to
dab67cf
Compare
Consider replacing the current logging module with a simple new module containing a |
Shading slf4j and logback is not of core concern and their release cycles match their own upstream vendors...I think it is best to externalize it to its own repository. |
But we indeed do the shading work, hiding this work in another repo[rocketmq-logging] doesn't change this truth. Furthermore, we have some customized configurators should belong to rocketmq repo. I think there is no one who wants to maintain the new repo rocketmq-logging in aliyun-mq organization. |
@lizhanhui Let's revert this merge and try get some feedbacks from the author @aaron-ai |
…)" This reverts commit 809ff6b.
OK, I will refine the shading part. |
* Remove ClientLogger * WIP * WIP * Rename logger to log * Make it compile * WIP * Fix bazel to use shaded slf4j * Fix DeleteExpiredCommitLogSubCommandTest * Fix pom.xml duplication * Fix maven deps * Add test logback configuration file * Fix unit test output * Fix logback configuration file * All logging are made on top of slf4j * Fix test log configuration file name * Fix test log configuration file name for test module * All logging are shaded slf4j targeted * DLedger has an explicit dependency on slf4j * Fix DLedger * Fix DLeader issue * Move logback configuration files to each module Co-authored-by: Li Zhanhui <lizhanhui@gmail.com>
Fixes #5484