I expect the vast majority of kafka users are using java for client apps,
and in most cases, they will just use the default jars they get in the
binary download.

I think the confusing thing here, is that there is a single jar file, that
includes all the broker, consumer and producer client code.  The 'broker'
is really just some scripts wrapped around launching the jvm with this jar
file.  If you download the binary, you also have scripts that launch
consumers and clients, using that same jar, just passing different command
line arguments.

So, really, there are not separate artifacts to speak of, from a broker,
consumer, producer stand point.   Good news, I understand there are plans
in the works to have separate jars for the broker, consumer clients,
producer clients, in 0.9.x.

Thanks for the info around 2.8.2 and beyond.  However, I think we'll try to
stay using 2.8.0 for the broker (since that seems to be the stable version
used at LinkedIn).  And in our env, we use a single artifact (via maven)
for all our broker and client apps.....

I don't think the issue in KAFKA-1163 is likely an upload issue (since when
I run 'sbt make-pom' locally, it builds it the same way as the broken one
uploaded to the public repo).

At the very least, I should think you'd want to remove the currently broken
one from the public repo, since from a maven standpoint, it's not
usable.....Perhaps a simple patch that only fixes the pom issue (call it

On Thu, Dec 5, 2013 at 9:43 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB