[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545331#comment-13545331
]
Joe Stein commented on KAFKA-133:
---------------------------------
this looks really good so far I was able to get ./sbt publish-local to run just
fine and integrate the result loca .iv2 with another sbt project I have using
"kafka" % "core-kafka_2.8.0" % "0.8.0-SNAPSHOT"
couple things
1) the groupID should be = org.apache
2) do you see any reason this would not run on the 0.7.2 branch? I am going to
propose a 0.7.3 release with this change also in there (less the metrics as
that is only in 0.8 and changes to version all minor details). I don't but
figure I would ask
notes for self: http://www.apache.org/dev/publishing-maven-artifacts.html
> 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
