[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499940#comment-13499940
]
Neha Narkhede commented on KAFKA-133:
-------------------------------------
* How come this is not Fix Version 0.8? Should it not be? Is it not planned for
the upcoming 0.8?
Just changed the affected version to 0.8
* Nobody is assigned. Is it known who will do this?
Anyone who is interested can pick this up. Feel free to assign this to
yourself.
* It looks like KAFKA-134 is marked as blocker, but it's also not assigned and
is not set for 0.8...?
KAFKA-134 is required only to be able to publish to maven using an sbt command.
For 0.8, if that is not ready, we can manually publish it. All the assignee
would do in this case, is figure out the procedure to get this done and post it
here. One of the committers can help roll the ball.
> 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
> 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
