Ok resolved:

1. the scripts in bin refer to target scala_2.8.0 even when building 2.9.2
target

2. sbt make-pom generates few conflicting dependencies including zkclient
On Feb 17, 2013 8:32 PM, "Michal Haris" <michal.ha...@visualdna.com> wrote:

> I have tried to build trunk and 0.8 branch today for the first time but
> failed:
>
> 1. When using sbt clean package there are some minor  warnings but it
> completes, however trying to run the server from packaged bin it exits with
> class kafka.Kafka not found.
>
> 2. When trying to use scala maven plugin, with which I can build 0.7.x
> branches (dependent on scala 2.8.0), after some tweaking of the generated
> kafka-core pom and having all dependencies I can't compile - get a type
> mismatch for Unit found zk Stat - has anybody tried to build 0.8 core only
> jar with maven ?
>
> Not sure what I'm doing wrong as my understanding of scala versions and
> sbt is minimal.
> On Jan 15, 2013 12:23 AM, "Neha Narkhede" <neha.narkh...@gmail.com> wrote:
>
>> Jane,
>>
>> I changed the version of scala in project/build.properties to 2.9.2 and
>> did
>> a ./sbt clean update package. It seems to build and run fine for me.
>>
>> I would check the classpath to see if there are conflicting versions of
>> scala.
>>
>> Thanks,
>> Neha
>>
>>
>> On Mon, Jan 14, 2013 at 1:22 PM, Jane Wang <ja...@twitter.com> wrote:
>>
>> > I need to use some of the newly added functions of kafka 0.8. However,
>> in
>> > our system,
>> > we support scala 2.9.2. I build my code together kafka 0.8 and scala
>> 2.9.2
>> > and I got alot
>> > of runtime issues, one of them is:
>> > Exception in thread "main" java.lang.NoClassDefFoundError:
>> > scala/Tuple2$mcLL$sp
>> > at kafka.producer.ProducerConfig.<init>(ProducerConfig.scala:29)
>> >
>> > I google searched and it seems there are also some people complaining
>> about
>> > the same
>> > issue but no real solution to it.
>> >
>> > Is kafka 0.8 compatible with scala 2.9.2? Can kafka 0.8 provide a build
>> > with scal 2.9.2?
>> >
>> > thanks,
>> > Jane
>> >
>>
>

Reply via email to