When we are talking about the setting in Build.scala there are two uses for it and we need to think of them separately.
The first is building and running the broker. The default for this is 2.8.0 The second is for building your client library (for producers/consumers) to work with the Kafka broker. In regards to Maven with Scala 2.10 the maven repository will only represent one of them (so it is kafka_2.10) as 2.10 is forward/back compatible with minor version. The 0.8.0 release has a kafka_2.10 version which works in 2.10.0, 2.10.1 and 2.10.2 My general rule with the broker is I build and run it in 2.8.0 and I do not think we should change the default (which to me represents what to build the broker in) until more production environments for the broker are on something other than 2.8.0 that we know can be supported. Run your client libraries in what ever Scala version you need/want they are separate things entirely. /******************************************* Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> ********************************************/ On Tue, Nov 5, 2013 at 1:59 PM, Ngu, Bob <bob....@intel.com> wrote: > Just to clarify, I also already have it working with 2.10.2 via this > setting change in Build.scala > scalaVersion := “2.10.2" > > My question is if this should be the default setting going on forth. Also > since I am using Maven and not sbt, I am not sure that the cross > publishing works as expected, does anyone know? > > Thanks, > Bob > > > > On 11/5/13, 7:19 AM, "Jun Rao" <jun...@gmail.com> wrote: > > >Kane, > > > >Would you mind attaching a patch to > >https://issues.apache.org/jira/browse/KAFKA-1116 to enable cross > >compilation to scala 2.10.2? > > > >Thanks, > > > >Jun > > > > > >On Mon, Nov 4, 2013 at 9:53 PM, Kane Kane <kane.ist...@gmail.com> wrote: > > > >> I'm using it with scala 2.10.2. > >> > >> On Mon, Nov 4, 2013 at 9:41 PM, Jun Rao <jun...@gmail.com> wrote: > >> > Do you think our cross compilation can be extended to scala 2.10.2? > >> > > >> > Thanks, > >> > > >> > Jun > >> > > >> > > >> > On Mon, Nov 4, 2013 at 9:48 AM, Ngu, Bob <bob....@intel.com> wrote: > >> > > >> >> Thanks, Kane I had the same problem with assembly-package-dependency > >>and > >> >> this fixes it. > >> >> > >> >> Jun, will scalaVersion be changed to 2.10.x? Currently it¹s set to > >>2.8.0 > >> >> and crossScalaVersions includes 2.10.1 but I believe that¹s to > >>publish > >> to > >> >> local ivy repo but I publish to local maven repo and I need to set > >> >> scalaVersion 2.10.2. Thoughts? > >> >> > >> >> Bob > >> >> > >> >> On 11/1/13, 9:36 PM, "Kane Kane" <kane.ist...@gmail.com> wrote: > >> >> > >> >> >Yes, I've had problem, which resolved with updating sbt-assembly. > >>Will > >> >> >open a ticket and provide a patch. > >> >> > > >> >> >On Fri, Nov 1, 2013 at 8:43 PM, Jun Rao <jun...@gmail.com> wrote: > >> >> >> Does the problem exist with trunk? If so, could you open a jira > >>and > >> >> >>submit > >> >> >> a patch? > >> >> >> > >> >> >> Thanks, > >> >> >> > >> >> >> Jun > >> >> >> > >> >> >> > >> >> >> On Fri, Nov 1, 2013 at 4:14 PM, Kane Kane <kane.ist...@gmail.com> > >> >> wrote: > >> >> >> > >> >> >>> I think > >> >> >>> addSbtPlugin("com.eed3si9n" % "sbt-assembly" % "0.8.8") > >> >> >>> > >> >> >>> Should be updated to 0.9.0 at least to successfully compile. I've > >> had > >> >> >>> an issue with assembly-package-dependency. > >> >> >>> > >> >> > >> >> > >> > >
