[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository

["Darren Sargent (JIRA)" <ji...@apache.org>]

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

Darren Sargent commented on KAFKA-133:
--------------------------------------

This ticket is marked as fixed, but the latest on the 0.8 branch still depends on an unpublished version of Yammer - this is from Build.scala:

 <dependency>
        <groupId>com.yammer.metrics</groupId>
        <artifactId>metrics-core</artifactId>
        <version>3.0.0-c0c8be71</version>
        <scope>compile</scope>
      </dependency>
      <dependency>
        <groupId>com.yammer.metrics</groupId>
        <artifactId>metrics-annotations</artifactId>
        <version>3.0.0-c0c8be71</version>
        <scope>compile</scope>
      </dependency>

Maven Central doesn't have a version anything like the one mentioned above: http://repo2.maven.org/maven2/com/yammer/metrics/metrics-core/
                
> 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, 0.8
>            Reporter: Neha Narkhede
>              Labels: patch
>             Fix For: 0.8
>
>         Attachments: KAFKA-133.patch, 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