travisdowns commented on issue #5347:
URL: https://github.com/apache/rocketmq/issues/5347#issuecomment-1289301245
> @travisdowns I think you are right. As a library, `rocketmq-tools` should
not introduce the facade and the implementation at the same time.
One question: does the current rocket-mq use the slf4j API implementation or
does it use any logback API directly?
I ask because the usual solution to this problem (when the offending library
can't be fixed or will only be fixed in a subsequent version) is to exclude the
logback-classic jar like so in the consuming project:
```
<exclusions>
<exclusion>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
</exclusion>
</exclusions>
```
I could apply this fix in openmessaging benchmark, but I want to check that
rocketmq does not use logback-classic API directly since if so this would break
that (since logback-classic will not be available at runtime).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
