[DERBY-3989] Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment can't be found but a Java 6 environment can be - ASF JIRA

XML

Word

Printable

JSON

This will make the build even more flexible. Probably involves the following changes:

1) Relaxing the requirement in PropertySetter that a Java 5 JDK must exist

2) Having PropertySetter look for a Java 6 JDK (and set java16compile.classpath accordingly) just as PropertySetter looks for a Java 5 JDK today

3) Changing the setCompilerProperties target in the master build script so that it

a) requires that java15compile.classpath or java16compile.classpath is set (it's ok for both to be set)

b) sets java15compile.classpath to ${jdbc3stubs}:${java16compile.classpath}

derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff
08/Jun/10 14:20
4 kB
Kristian Waagan
derby-3989-01-ac-optionalJava5.diff
13/Jan/09 17:58
15 kB
Richard N. Hillegas
derby-3989-01-ab-optionalJava5.diff
09/Jan/09 16:40
12 kB
Richard N. Hillegas
derby-3989-01-aa-optionalJava5.diff
08/Jan/09 23:17
10 kB
Richard N. Hillegas

depends upon

DERBY-3988 Set the Java 6 complilation path based on the Java 5 compilation path so that the JDBC4 support is always built

incorporates

DERBY-4699 Build breaks if a Java 6 JDK is detected when compiling with a Java 5 compiler