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 to go through in that ticket it seems) will try some of the patch applys tomorrow and see how they go. I would be in favor of it being part of the 0.8.0 final if it all gets through and looks good and committing it to the 0.8 branch and not only trunk but lets see first what is involved building 2.10.0, 2.10.1 and 2.10.2 and what is going to take to get it working with the patches submitted.
On Sun, Jul 14, 2013 at 9:44 PM, chetan conikee <[EMAIL PROTECTED]> wrote:
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 fine (so I'm not particularly inclined to change, but I'm just curious).
One thing I notice, in the pom file, there are 2 dependencies listed for zookeeper, one of which has an exclusion clause, the other does not. I assume this is not intended: <dependency> <groupId>org.apache.zookeeper</groupId> <artifactId>zookeeper</artifactId> <version>3.3.4</version> <exclusions> <exclusion> <groupId>log4j</groupId> <artifactId>log4j</artifactId> </exclusion> <exclusion> <groupId>jline</groupId> <artifactId>jline</artifactId> </exclusion> </exclusions> </dependency>
and then <dependency> <groupId>org.apache.zookeeper</groupId> <artifactId>zookeeper</artifactId> <version>3.3.4</version> </dependency> On Sun, Jul 14, 2013 at 7:06 PM, Joe Stein <[EMAIL PROTECTED]> wrote:
Subject: Re: 0.8.0-beta1 is now available in public maven
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 doing in https://issues.apache.org/jira/browse/KAFKA-974
Please create a JIRA however I suspect when we do another release (either 0.8.0-beta2 or 0.8.0) this will be correct and 1:1 from apache repo because I won't be doing multiple pushes like i had to-do here
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 <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext