[ 
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495769#comment-13495769
 ] 

Otis Gospodnetic edited comment on KAFKA-133 at 11/13/12 12:45 AM:
-------------------------------------------------------------------

Coda Hale metrics does seem to be in Maven repo already, see: 
http://mvnrepository.com/artifact/com.yammer.metrics
Though from KAFKA-585 it looks like there may be a dependency on Metrics 3.*, 
which is not in any Maven repo yet.

Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not 
treated as external dependencies?
Oh, is that zkclient Stefan's zkclient? This one: 
http://mvnrepository.com/artifact/com.github.sgroschupf/zkclient/0.1 but 
locally modified, jarred, and stuck in svn?
Maybe we could instead provide a patch for zkclient and get zkclient 
maintainer(s) to apply it?  I knows Stefan personally and could bug him about 
it.... he is a busy CEO these days, but maybe somebody else on his team could 
get this done.

                
      was (Author: otis):
    Coda Hale metrics does seem to be in Maven repo already, see: 
http://mvnrepository.com/artifact/com.yammer.metrics
Though from KAFKA-585 it looks like there may be a dependency on Metrics 3.*, 
which is not in any Maven repo yet.

Custom zkclient jar... maybe a Kafka developer in the know can jump in?
Maybe this jar could be included/hidden in one of the Kafka jars, so it is not 
treated as external dependencies?
                  
> 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

Reply via email to