filed: https://issues.apache.org/jira/browse/KAFKA-978
I can try to take a look, can you point me to where/how you generate the
pom file?
On Tue, Jul 16, 2013 at 7:26 AM, Joe Stein wrote:
> Hi Jason, there are two different answers in regards to Scala version in my
> opinion as there are clea
Hi Jason, there are two different answers in regards to Scala version in my
opinion as there are clear distinctions between broker and
producers/consumers.
I don't know what the mix is but experience with brokers is only building
and running in production 2.8.0 and I suspect this is the same for o
Any thoughts on my question, wrt scala version to prefer? Also, what of
the double dependency on zookeeper? Should I file a jira for that?
Jason
On Sun, Jul 14, 2013 at 9:26 PM, Jason Rosenberg wrote:
> Thanks for doing this!
>
> I'm wondering whether there is a reason to prefer one version
Hey Joe,
Awesome. I've updated the Jira:
https://issues.apache.org/jira/browse/KAFKA-974
Cheers,
Chris
On 7/15/13 11:24 AM, "Joe Stein" wrote:
>hmmm, interesting
>
>I think the issue is that I had to-do multiple pushes to nexus to get this
>to work (unfortunately) and perhaps maven centra
hmmm, interesting
I think the issue is that I had to-do multiple pushes to nexus to get this
to work (unfortunately) and perhaps maven central did not overwrite like it
did with apache rather appending and meshing the poms together. The POM in
maven central looks like a combination of what I was
Hey Guys,
Digging into this more. Here's a fun fact: Maven Central's POM does not
match Apache release's.
http://search.maven.org/remotecontent?filepath=org/apache/kafka/kafka_2.9.2
/0.8.0-beta1/kafka_2.9.2-0.8.0-beta1.pom
https://repository.apache.org/content/groups/public/org/apache/
Hey Guys,
The problem persists, even when using the explicit URL Joe provided.
I've also constructed a dummy Maven project, and tested Kafka dependencies
there. That worked, but I had to explicit write the block.
I might have to sick our local Gradle experts on this one...
Cheers,
Chris
On 7/
I stumbled on a few issues when I was attempting to create a Scala based
Client (Producer/Consumer) project.
Finally worked after revisions:
Here's the snippet of by build.sbt
~~
/* scala versions and options */
scalaVersion := "2.9.2"
libraryDependencies +=
"org.apache.kafka" %
Hey Joe,
I can give that a shot. I did have to add the apache release repository to
get kafka to resolve.
I'll get back to you in a few.
Cheers,
Chris
On 7/15/13 10:43 AM, "Joe Stein" wrote:
>I wonder if Gradle does not use Maven Central as the default repository
>like SBT does maybe you have
I wonder if Gradle does not use Maven Central as the default repository
like SBT does maybe you have to explicitly set this (shot in the dark,
don't know Gradle).
Maven Central Repository for resolver = http://repo1.maven.org/maven2/
On Mon, Jul 15, 2013 at 1:39 PM, Chris Riccomini wrote:
> Hey
Hey Joe,
The error I see is:
10:35:30.431 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build
failed with an exception.
10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter]
10:35:30.432 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
10:35:30.432 [ERROR] [org.gradle.Buil
What is/are the error(s) you are getting?
"intransitive" in the SBT line is so that SBT does not fetch the libraries
what is set for exclusion in the POM
an example of an error if you don't do use what should be excluded is in
https://issues.apache.org/jira/browse/KAFKA-974
On Mon, Jul 15, 2013
Hey Joe,
First off, thanks for doing this!
I'm trying to use the publication with Gradle, and I'm running into
problems. It's giving me a funky exception. I did some digging, and
apparently the exception implies that Gradle has been given a 1.0 pom.
I took a look at the Kafka pom:
https://
My company, and I am sure many other companies too, use Kafka in
conjunction with other libraries/frameworks/platforms which may depend on
newer versions of Scala than 2.[8-9].
Scala 2.10 and up has been around for many months already and always
evolving/improving project such as Kafka should keep
Thanks for doing this!
I'm wondering whether there is a reason to prefer one version of scala over
another, if we don't have any other particular scala dependency in our
code. Are the newer versions better/more efficient, some how? We've
essentially been using 2.8.0 so far, which seems to be fin
SBT uses Maven Central as a default repository (local ivy too).
The artifacts are published to Maven Central so nothing you should have
to-do except to specify the libraryDependencies
In regards to 2.10.X support I took a really quick look at
https://issues.apache.org/jira/browse/KAFKA-717 (lots
Excellent
What about the resolver ? sonatype, typeafe. maven artifactory ?
Any plans for a 2.10+ compile as well
On Sun, Jul 14, 2013 at 6:37 PM, Dima Gutzeit wrote:
> What about the "newer" (not so new anymore) scala version 2.10.0 and up ?
> When will it be supported officially ?
>
>
> Regar
What about the "newer" (not so new anymore) scala version 2.10.0 and up ?
When will it be supported officially ?
Regards,
Dima Gutzeit.
On 15/7/13 9:32 AM, "Joe Stein" wrote:
>With SBT you can use 0.8.1-beta built with any of these four Scala
>versions
>in libraryDependencies now
>
>"org.apac
With SBT you can use 0.8.1-beta built with any of these four Scala versions
in libraryDependencies now
"org.apache.kafka" % "kafka_2.9.2" % "0.8.0-beta1" intransitive()
or
"org.apache.kafka" % "kafka_2.9.1" % "0.8.0-beta1" intransitive()
or
"org.apache.kafka" % "kafka_2.8.2" % "0.8.0-beta1" in
19 matches
Mail list logo
