You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/05/23 20:40:13 UTC
[jira] [Comment Edited] (BEAM-304) Build break: maven is picking up
Kafka snapshots
[ https://issues.apache.org/jira/browse/BEAM-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297042#comment-15297042 ]
Daniel Halperin edited comment on BEAM-304 at 5/23/16 8:40 PM:
---------------------------------------------------------------
I lied! What actually happened is that Kafka *released* 0.10, even though you can't actually find it in any of the Maven repo websites. (Usual asynchronous sync issues).
So this is all WAI and we just needed to pin to 0.9.
Resolving.
was (Author: dhalperi@google.com):
I lied! What actually happened is that Kafka *released* 0.10, even though you can't actually find it in any of the Maven repo websites. (Usually asynchronous sync issues).
So this is all WAI and we just needed to pin to 0.9.
Resolving.
> Build break: maven is picking up Kafka snapshots
> ------------------------------------------------
>
> Key: BEAM-304
> URL: https://issues.apache.org/jira/browse/BEAM-304
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-extensions
> Reporter: Daniel Halperin
> Assignee: Daniel Halperin
> Priority: Critical
>
> A few concurrent issues:
> 1. We did not pick a specific version of Kafka in our pom, instead we just dependended on 0.9+
> 2. It looks like Kafka has deployed a 0.10 snapshot
> 3. For some reason, our build is picking up snapshot versions instead of using only things available on Maven central.
> 4. 0.10 version of KafkaIO has a breaking change that breaks our code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)