If you go this way, you're still left with two issues if you want
adoption to be smooth:
* KAFKA-133 which makes integrating clients hard otherwise
* Maybe building recipes for creating standard packages (rpm + deb)
Most people will install and configure kafka from a CM system (puppet,
chef or
Chris,
Thanks for stepping up to help here. Based on feedback from various members
on general@, I think it is wiser to do the source release, with the README
having a How to build and download dependencies section.
We still have to go through all the jars we package in our source release,
and
On 12/03/2011 02:40 PM, Chris Burroughs wrote:
My reading is that since we would only be distributing source code, the
NOTICE file should not reflect binary dependencies and would have *only*
the standard Apache bit [3]. Same for LICENSE.
I suppose any jar's checked into svn would complicate
