[
https://issues.apache.org/jira/browse/SAMZA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042371#comment-14042371
]
Martin Kleppmann commented on SAMZA-284:
----------------------------------------
Sadly, the snapshot jars have disappeared again, which suggests that there is
some daily process that cleans them. :( Looks like our options are:
* Ask the Kafka team nicely whether they could run an official (non-snapshot)
release soon.
* Host our own Maven repository just for the test jars, e.g. on
[S3|http://blog.brickcitylabs.com/2012/02/hosting-maven-repository-on-amazons-s3.html]
or [Github|http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/] or
on the personal web space provided to Apache committers. (Some might consider
that an ugly hack, but it wouldn't be our first non-Apache repository
reference: we're already relying on Typesafe's Maven repository.)
* Wait for INFRA to get back to us with a recommendation.
What do you think?
> Resolve bundled Kafka jar issue
> -------------------------------
>
> Key: SAMZA-284
> URL: https://issues.apache.org/jira/browse/SAMZA-284
> Project: Samza
> Issue Type: Sub-task
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: SAMZA-284.patch
>
>
> We are currently bundling the test jars for Kafka 0.8.1 for Scala 2.9 and
> 2.10. These jars have not yet been published in Maven, so we need to either
> get them published or remove the jars from the distribution and work around
> the issue. The former solution is much preferred.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
