[
https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651076#action_12651076
]
Patrick Hunt commented on ZOOKEEPER-233:
----------------------------------------
@Doug: that's how I usually do it.
I'm assuming we are talking about:
zookeeper-client-<version>.jar - all classes necessary to run client, incl
generated marshalling code
zookeeper-server-<version>.jar - all of the classes that are part of ZK, except
for that in zookeeper-client jar
This would be a non-bwcompat change -- ie build, scripts
(zkServer.sh/zkClient.sh), release packaging, etc.. would have to change.
or should we have three - client, server, common (marshalling code, etc...)? In
case we find more reasons to create additional "specialized" jars.
We have 1 vote from doug to have disjoint, anyone else?
> 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
> Reporter: Hiram Chirino
> Assignee: Patrick Hunt
> Priority: Trivial
>
> 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.
-
You can reply to this email to add a comment to the issue online.
