PJ Fanning created ZOOKEEPER-4820:
-------------------------------------
Summary: zookeeper pom leaks logback dependency
Key: ZOOKEEPER-4820
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4820
Project: ZooKeeper
Issue Type: Task
Components: java client
Reporter: PJ Fanning
Since v3.8.0
https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper/3.8.0
It's fine that Zookeeper uses Logback on the server side - but users who want
to access Zookeeper using client side code also add this zookeeper jar to their
classpaths. When zookeeper is used as client side lib, it should ideally not
expose a logback dependency - just an slf4j-api jar dependency.
Would it be possible to repwork the zookeper pom so that client side users
don't have to explicitly exclude logback jars? Many users will have their own
preferred logging framework.
Is there another zookeeper client side jar that could be instead of
zookeeper.jar?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
