[ZOOKEEPER-4820] zookeeper pom leaks logback dependency

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: java client
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: PJ Fanning
• Created: 27/Mar/24 16:32
• Updated: 11/Apr/24 23:41

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

Issue Links

• duplicates: ZOOKEEPER-4763 Logback dependency should be scope provided/test
• links to: GitHub Pull Request #2155