[
https://issues.apache.org/jira/browse/ZOOKEEPER-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PJ Fanning updated ZOOKEEPER-4820:
----------------------------------
Description:
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 rework 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?
was:
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?
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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 rework 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)
