[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561100#comment-13561100
]
Scott Carey commented on KAFKA-133:
-----------------------------------
0.8.x needs to depend on a released version of metrics.
I currently use yammer-metrics in my code, and was excited to see that kafka
was going to use metrics so that we could clean up and standardize things
there. However, since it depends essentially on trunk (3.0.0-SNAPSHOT)
including Kafka 0.8 breaks and there is no release plan or date for when 3.0.0
will even exist.
Even worse, if we try and compile against the CURRENT yammer-metrics head
3.0.0-SNAPSHOT kafka fails to compile because it is ... trunk and things change.
0.8.x needs to depend on a released version of metrics.
> 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
