Rick Hillegas <[email protected]> writes: > I have just sync'd to the head of the trunk and the build is now > broken for me: > > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [java] Warning: Lookahead adequacy checking not being performed > since option LOOKAHEAD is more than 1. Set option FORCE_LA_CHECK to > true to force checking. > [java] Warning: ParseException.java: File is obsolete. Please > rename or delete this file so that a new one can be generated for you. > [java] Warning: Token.java: File is obsolete. Please rename or > delete this file so that a new one can be generated for you. > [java] Warning: CharStream.java: File is obsolete. Please rename > or delete this file so that a new one can be generated for you. > [javac] > /Users/rh161140/derby/mainline/trunk/java/engine/org/apache/derby/iapi/jdbc/FailedProperties40.java:27: > cannot access java.util.HashMap > [javac] bad class file: > /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Classes/alt-rt.jar(java/util/HashMap.class) > [javac] class file has wrong version 50.0, should be 49.0 > [javac] Please remove or make sure it appears in the correct > subdirectory of the classpath. > [javac] import java.util.HashMap; > [javac] ^ > [javac] 1 error > > BUILD FAILED
Hi Rick, It looks like your ant is using the Java 5 compiler (check JAVA_HOME), which doesn't know how to access read classes in the Java 6 class library. Could that be the case? Does it work if you point JAVA_HOME to a JDK 6 installation? With some older releases of Sun's JDK 6, such a combination would work because the class libraries used the Java 5 class format. This has changed in later releases of JDK 6, so now you cannot access the Java 6 class library from Java 5. -- Knut Anders
