I think Sasi's comment was along the right lines. If you specify the Storm version in your own POM it will take precedent over the version specified in storm-kafka-0.8-plus. Note that storm 0.9.0.1 fixes the issue of Java 7 binaries.
On Tue, Jan 14, 2014 at 12:24 PM, Krishnanand Khambadkone < [email protected]> wrote: > Adam, thank you for the tips. Unfortunately moving to java 7 is not an > option for me. Even moving to a higher version of 1.6 (1.6_51 and above) > breaks hadoop and creates a mess. Is there a workaround for this, such > as specifying the source and target version in pom.xml or some such thing. > > > > > On Tuesday, January 14, 2014 6:31 AM, Adam Lewis <[email protected]> > wrote: > I've found that Maven can drift away from MacOS in terms of which java > version they use (even if you have your preferred version on the path and > JAVA_HOME). Did you compare java -version and mvn -version? Something is > getting built by Java 7; the latest storm-kafka-0.8-plus pom on github > depends on storm 0.9.0 which was accidentally built using Java 7, check out > storm 0.9.0.1 for Java6 version...or move to Java 7 if you can. > > > On Tue, Jan 14, 2014 at 2:00 AM, Krishnanand Khambadkone < > [email protected]> wrote: > > Hi, When I do a mvn package I get this message > > Tests in error: > > testMultiplePartitionsOnDifferentHosts(storm.kafka.DynamicBrokersReaderTest): > backtype/storm/utils/Utils : Unsupported major.minor version 51.0 > testSwitchHostForPartition(storm.kafka.DynamicBrokersReaderTest): > backtype/storm/utils/Utils > testGetBrokerInfo(storm.kafka.DynamicBrokersReaderTest): > backtype/storm/utils/Utils > testMultiplePartitionsOnSameHost(storm.kafka.DynamicBrokersReaderTest): > backtype/storm/utils/Utils > > My java version is, on mac os x 10.7.5 > > java version "1.6.0_29" > Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-11M4609) > Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode) > > > > >
