Except that it still has the annoying feature of naming the kafka version
after the scala version, which doesn't make sense, e.g.:

~/.ivy2/local/org.apache/kafka_2.8.0/0.8.0-SNAPSHOT/poms ls -l
total 24
-rw-r--r--  1 jbr  jbr  3786 May  7 13:43 kafka_2.8.0.pom
-rw-r--r--  1 jbr  jbr    32 May  7 13:44 kafka_2.8.0.pom.md5
-rw-r--r--  1 jbr  jbr    40 May  7 13:44 kafka_2.8.0.pom.sha1


~/.ivy2/local/org.apache/kafka_2.8.0/0.8.0-SNAPSHOT ls -l jars
total 4640
-rw-r--r--  1 jbr  jbr  2367457 May  6 15:54 kafka_2.8.0.jar
-rw-r--r--  1 jbr  jbr       32 May  7 13:44 kafka_2.8.0.jar.md5
-rw-r--r--  1 jbr  jbr       40 May  7 13:44 kafka_2.8.0.jar.sha1

I think it was mentioned previously (0.7.x had the same issue) there's an
easy way to fix this (but I don't remember at the moment).  Perhaps we
could get this fixed before releasing?

I'd think the maven artifacts should be named 'kafka_0.8.0.pom' or
'kakfa_0.8.0-SNAPSHOT.pom', etc...

On Tue, May 7, 2013 at 1:48 PM, Jason Rosenberg <[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