[
https://issues.apache.org/jira/browse/SAMZA-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938422#comment-13938422
]
Chris Riccomini commented on SAMZA-185:
---------------------------------------
+1
lol, yeah I gave it a shot on Friday, and then unassigned it, and went home. :)
The excludes you've done are correct.
The SNAPSHOT jars included were custom built by me. Kafka's SBT build was
updated to publish -test jars, but that appears to have been lost in their
Gradle migration. Could you open a KAFKA ticket to get them to re-add it in
gradle? In the mean time, we have two options: keep what we've got, or checkout
a fresh Kafka 0.8.1 branch, and tweak gradle ourselves to build the test jars
(and probably submit the patch to the KAFKA JIRA). Given that they're just test
JARs, and we use them in a pretty limited capacity, I don't have an opinion on
what's the right approach here, as long as the KAFKA JIRA gets filed. I'll
leave it up to you.
Either way, commit at will.
> Upgrade Samza to Kafka 0.8.1
> ----------------------------
>
> Key: SAMZA-185
> URL: https://issues.apache.org/jira/browse/SAMZA-185
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Martin Kleppmann
>
> We should upgrade Kafka to 0.8.1. This involves:
> 1. Switch to using Kafka's maven dependencies
> (http://repo.maven.apache.org/maven2/org/apache//kafka/kafka_2.10/0.8.1/)
> instead of checking in JARs.
> 2. Upgrade build.gradle and gradle dependency versions to depend on 0.8.1.
> 3. Update index.md in docs to no longer say "It depends on a snapshot version
> of Kafka that will not officially be released for a few months."
--
This message was sent by Atlassian JIRA
(v6.2#6252)
