[ 
https://issues.apache.org/jira/browse/ROCKETMQ-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383517#comment-16383517
 ] 

ASF GitHub Bot commented on ROCKETMQ-359:
-----------------------------------------

coveralls commented on issue #221: [ROCKETMQ-359] Replace slf4j api used in 
RocketMQ with InternalLogger
URL: https://github.com/apache/rocketmq/pull/221#issuecomment-359795067
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/15775789/badge)](https://coveralls.io/builds/15775789)
   
   Coverage decreased (-0.2%) to 41.005% when pulling 
**9218f41044ebec85d74ac84c1db42cad384fde0c on lindzh:fix_client_log_full** into 
**c19fa25c87d6f6a7e5af7eab99910c271173225f on apache:develop**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)

Reply via email to