[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Stein updated KAFKA-133:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I committed this with 2 minor changes
1) removed the commented out line of code that is not needed anymore
2) overrode the organization to be org.apache so the groupId shows up as such
sbt works for using this locally now
"org.apache" % "core-kafka_2.8.0" % "0.8.0-SNAPSHOT"
it is a great step forward toward for helping folks to use the core code.
thanks!
any other issues that come up I will follow-up accordingly with them and will
shepherd that we publish once released (since we are not there yet it is
premature but saw no reason to not get these changes up in trunk and resolve
this ticket)
> 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
