[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498597#comment-13498597 ]
Otis Gospodnetic commented on KAFKA-133: ---------------------------------------- FYI just emailed Stefan asking if zkclient 0.2 could be cut and published in Maven. He replied a few minutes later from a cab and CCed his colleague asking him to do this, so if stars align, you may see zkclient 0.2 out and you can remove it from Kafka. And then I really really hope you can publish Kafka to a Maven repo! :) Questions/comments: * How come this is not Fix Version 0.8? Should it not be? Is it not planned for the upcoming 0.8? * Nobody is assigned. Is it known who will do this? * It looks like KAFKA-134 is marked as blocker, but it's also not assigned and is not set for 0.8...? > Publish kafka jar to a public maven repository > ---------------------------------------------- > > Key: KAFKA-133 > URL: https://issues.apache.org/jira/browse/KAFKA-133 > Project: Kafka > Issue Type: Improvement > Affects Versions: 0.6 > Reporter: Neha Narkhede > Labels: patch > Attachments: pom.xml > > > The released kafka jar must be download manually and then deploy to a private > repository before they can be used by a developer using maven2. > Similar to other Apache projects, it will be nice to have a way to publish > Kafka releases to a public maven repo. > In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, > but ran into some authentication problems. It will be good to revisit this > and get it resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira