[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141059#comment-13141059
 ] 

Thomas Koch commented on ZOOKEEPER-233:
---------------------------------------

Copying the description of ZOOKEEPER-1003 from Jean-Pierre König (jpkoenig) 
here:

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.

                
> Create a slimer jar for clients to reduce thier disk footprint.
> ---------------------------------------------------------------
>
>                 Key: ZOOKEEPER-233
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-233
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: build, java client
>            Reporter: Hiram Chirino
>            Priority: Trivial
>             Fix For: 3.5.0
>
>
> Patrick request I open up this in issue in this [email 
> thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]

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


Reply via email to