Hiram Chirino commented on ZOOKEEPER-80:


Here are my 2 cents for how to implement this so it co-exists nicely with 

For java at least, you want to group lots of small disjoint contributions into 
one jar.  If they become more massive, it may be worth splitting it out to 
independent jars, but simplicities sake/maintenance needed to manage small 
contributions, one jar should be enough.  The only tricky bit is that we also 
want to support implementing the recipe in other languages, so we want to also 
support multiple module directories.

So my proposal is to have a module which would mainly hold the general 
documentation for the protocol which should be language agnostic:

And then we just have sub modules for the implementation of those recipes for 
the different languages.
The java module would use maven directory layouts

The c stuff would standard GNU c source layout

ruby would use what every ruby folks are used to.

Also note that it might be better to replace 'recipes' term with 'protocols'.

> Document process for client recipe contributions
> ------------------------------------------------
>                 Key: ZOOKEEPER-80
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-80
>             Project: Zookeeper
>          Issue Type: Task
>          Components: documentation
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
> Per Doug's suggestion I'll use a link instead of copy/paste:
> http://mail-archives.apache.org/mod_mbox/hadoop-zookeeper-dev/200807.mbox/[EMAIL

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to