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

Alan Cabrera edited comment on KAFKA-133 at 9/29/11 5:35 PM:
-------------------------------------------------------------

I need to state the obvious, because I am a mentor, but while it's good to get 
this machinery working, this project cannot actually publish any artifacts 
until its first official release.
                
      was (Author: maguro):
    I need to state the obvious, because I am a mentor, but while it's good to 
get this machinery working, this project cannot actually publish any artifacts 
yet.
                  
> 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
>            Reporter: Neha Narkhede
>
> 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

        

Reply via email to