Daniel John Debrunner wrote:
Sean Qiu wrote:
Do you mean we can build derby with ${j14lib} points to jdk 1.5 or
higher?
Well it works for me with IBM's 1.5 jvm on trunk (& I guess 10.3 branch
would work as well, I doubt it will work on 10.2 or earlier).
j14lib=c:/_work/p4n/djdcs/ibm15/jre/lib
java14compile.classpath=C:/_work/p4n/djdcs/ibm15/jre/lib/vm.jar;C:/_work/p4n/djdcs/ibm15/jre/lib/core.jar;C:/_work/p4n/djdcs/ibm15/jre/lib/server.jar;C:/_work/p4n/djdcs/ibm15/jre/lib/xml.jar;C:/_work/p4n/djdcs/ibm15/jre/lib/ibmjcefw.jar;C:/_work/p4n/djdcs/ibm15/jre/lib/security.jar
Just to add, as Knut Anders said, you need to have JAVA_HOME set to your
1.5 JVM. The properties above (j14lib & java14compile.classpath) do
*not* affect which JDK is used to build Derby, that's driven by ant.
They only affect the classpath used for the core Java library.
In fact looking at the build system, if you set java14compile.classpath
then j14lib will be ignored. j14lib is only used to set the default
value for java14compile.classpath which probably only works for Sun's
1.4 JDK.
Dan.
