onobc opened a new issue, #19484: URL: https://github.com/apache/pulsar/issues/19484
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version - **OS:** `<not applicable>` - **Pulsar:** `2.11.0` ### Minimal reproduce step ### Problem The `pulsar-client-all:2.11.0` dependency transitively includes Log4j2 (see [ here](https://mvnrepository.com/artifact/org.apache.pulsar/pulsar-client-all/2.11.0)) rather than just the SLF4J api and logging bridge. Whereas the `pulsar-client-all:2.10.3` does **NOT** bring a logging impl in (see [here](https://mvnrepository.com/artifact/org.apache.pulsar/pulsar-client-all/2.10.3)). ### Symptoms If the consuming app is already using a logger impl then a conflict can occur at startup (when using SLF4J) telling user to pick one or the other. If the consuming application is not already using a logger impl then `pulsar-client-all` effectively chooses LOG4J2 for the app. ### What did you expect to see? Adding the dependency `org.apache.pulsar:pulsar-client-all:2.11.0` should **NOT** transitively bring in the log4j2 implementation. ### What did you see instead? Adding the dependency `org.apache.pulsar:pulsar-client-all:2.11.0` transitively **DID** bring in the log4j2 implementation. ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
