[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496860#comment-13496860
]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
>> So is the blocker for this issue the fact that there is a custom zkclient?
I believe so.
>> Should the modified API be provided as a patch to the original zkclient?
It is already checked into zkclient trunk
>> Should the zkclient maintainers be nudged to publish the new zkclient to a
>> Maven repo?
Sure, please feel free to ping them.
> 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
