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
The one difference from the IBM 1.4 setup is that vm.jar is needed in
java14compile.classpath.
Note this doesn't mean that one can use 1.5 features in the code as the
base is still JDK 1.4/J2ME/CDC/Foundation. The build.xml files use the
-target 1.4 and -source 1.4 flags for most of the code.
It does have the risk that one can introduce a change that depends on a
1.5 class or method, such as Integer.valueOf(int), since the libraries
pointed to are the 1.5 ones (java14compile.classpath). -target and
-source do not change the core library level. The -target changes the
version of the -class file, the -source the level Java language syntax.
However, it does allow anyone to compile using a 1.5 level compiler.
I wrote:
I'm able to build using IBM's 1.5 SDK with no problems.
HTH,
Dan.
