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
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
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
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
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
