[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxime Brugidou updated KAFKA-133:
----------------------------------
Attachment: KAFKA-133.patch
Taking Otis notes into account, Here is the simplest patch I could make, that
applies cleanly on 0.8:
Here are the changes:
* Version is 0.8.0-SNAPSHOT until 0.8.0 becomes stable
* You need to change the publish URL and credentials location
* Use com.101tec.zkclient 0.2
* Use com.yammer.metrics.metrics-* 3.0.0-SNAPSHOT (I had to use snapshot
because there is no 3.0.0 stable)
* Use org.slf4j.slf4j-simple 1.6.4 ("latest.release" was used)
To publish:
* ./sbt publish-local && ./sbt publish
This will create a pom for kafka that depends on all the subprojects. The
"main" project that you generally want to use is core-kafka_2.8.0 like this:
<dependency>
<groupId>kafka</groupId>
<artifactId>core-kafka_2.8.0</artifactId>
<version>0.8.0-SNAPSHOT</version>
</dependency>
> 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
