[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134383#comment-13134383
]
Joshua Hartman commented on KAFKA-133:
--------------------------------------
I came into Mountain View today on a loooong train ride and my internet died
right after I posted this. I wanted to say that it wasn't quite ready, but that
we should sit down today and go through this so we can perfect it for kafka's
long term needs.
Chris Riccomini reminded me about this on Friday and I promised myself I would
finish it over the weekend - I think I'm about 3 weeks overdue.
> 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
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
