build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3

• Key: DERBY-3560
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Kathey Marsden
• Reporter: Kathey Marsden
• Component/s: Build tools
• Affects Version/s: 10.3.3.0
• Fix Version/s: 10.3.3.0

Description

Bryan reported this issue after the change to print thread dumps on 10.3 with stress.multi when he didn't have jdk16 set. The build of ThreadDump should not occur if jdk16 is not set.

/home2/bpendleton/src/derby/10_3/10.3/java/testing/build.xml:62: The following error occurred while executing this line:
/home2/bpendleton/src/derby/10_3/10.3/java/testing/org/apache/derbyTesting/functionTests/util/build.xml:104: Error running ${jdk16}/bin/javac compiler

Comments

[Kathey Marsden]

Attached is a patch to fix this issue. It only builds the ThreadDump class if jdk16 is set. This means that for 10.3 if the class wasn't built and stress.multi tries to dump stack traces, because the test failed to shutdown the threads, the stress.log may print a ClassNotFoundException instead. With this patch, on 10.3, you will get stack traces only if both jdk16 was set when you build and you run with jdk15 or higher.

trunk and 10.4 do not have the jdk16 build requirement because we have and can use ${java15compile.classpath} there.

[Kathey Marsden]

Committed patch to 10.3. On 10.3 thread dumps will only print if jdk16 is set during build.