[
https://issues.apache.org/jira/browse/ROCKETMQ-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lindzh updated ROCKETMQ-359:
Description:
Since Logger is used any where and there is many loggers for us to choose,In
many cases we have to isolate our logger with other loggers. In my opinion use
an isolated logger is necessary.
- logging isolation has been fix with logging component
And it is necessary to replace slf4j api used in RocketMQ with InternalLogger
now!
was:
Since Logger is used any where and there is many loggers for us to choose,In
many cases we have to isolate our logger with other loggers. In my opinion use
an isolated logger is necessary.
- logging isolation has been fix with logging component
And it is necessary to replace slf4j api used in RocketMQ w
> Replace slf4j api used in RocketMQ with InternalLogger
> --
>
> Key: ROCKETMQ-359
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-359
> Project: Apache RocketMQ
> Issue Type: Improvement
>Affects Versions: 4.2.0
>Reporter: lindzh
>Assignee: vongosling
>Priority: Major
> Fix For: 4.3.0
>
>
> Since Logger is used any where and there is many loggers for us to choose,In
> many cases we have to isolate our logger with other loggers. In my opinion
> use an isolated logger is necessary.
> - logging isolation has been fix with logging
> component
> And it is necessary to replace slf4j api used in RocketMQ with InternalLogger
> now!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
