[ https://issues.apache.org/jira/browse/ZOOKEEPER-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Koch resolved ZOOKEEPER-1003. ------------------------------------ Resolution: Duplicate I've created a subissue in ZOOKEEPER-233, so closing this later duplicate to avoid splitting the discussion. I've subscribed the watchers of this issue to ZOOKEEPER-233. > provide a separate client library jar > -------------------------------------- > > Key: ZOOKEEPER-1003 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1003 > Project: ZooKeeper > Issue Type: Wish > Reporter: Jean-Pierre Koenig > Labels: client, dependencies, library, maven > > This feature request applies to ZooKeeper, HBase, Hadoop and maybe other > projects. Currently, to use one of these projects, I need to include one big > jar file as a dependency, that > - contains the complete server code, > - contains much more code then I use > - and most annoyingly depends on many other jars, that are mostly needed for > the > server but not for the client library. > Thus when using maven and including any of the mentioned projects, the > dependency graph of my projects grows unnecessarily large. > This is a severe problem for at least two reasons: > - The probability of conflicting dependencies (versions) gets boosted. > - Especially for mapreduce jobs depending on HBase or Zookeeper, the jars > sent to the > clusters grow to beyond 20-30MB of unnecessary dependencies. > One could work around the problem with maven dependency exclusions, but this > may lead to unpredictable runtime errors (ClassNotFound) since dependency > management is not save on compile time only. > I wish we could solve the underlying issue at the root with a client library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira