You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/03/20 19:31:25 UTC
[jira] Created: (DERBY-3560) build failure: Error running
${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
------------------------------------------------------------------------------------
Key: DERBY-3560
URL: https://issues.apache.org/jira/browse/DERBY-3560
Project: Derby
Issue Type: Bug
Components: Build tools
Affects Versions: 10.3.2.2
Reporter: Kathey Marsden
Assignee: Kathey Marsden
Priority: Minor
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (DERBY-3560) build failure: Error running ${jdk16}/bin/javac
compiler if jdk16 is not set on 10.3
Posted by Bryan Pendleton <bp...@amberpoint.com>.
> Kathey Marsden resolved DERBY-3560.
> -----------------------------------
>
> Committed patch to 10.3. On 10.3 thread dumps will only print if jdk16 is set during build.
Thanks Kathey! This seems like a good resolution to me.
bryan
[jira] Resolved: (DERBY-3560) build failure: Error running
${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3560.
-----------------------------------
Resolution: Fixed
Committed patch to 10.3. On 10.3 thread dumps will only print if jdk16 is set during build.
> build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3560
> URL: https://issues.apache.org/jira/browse/DERBY-3560
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.3.2.2
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3560_diff.txt
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-3560) build failure: Error running
${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-3560.
---------------------------------
> build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3560
> URL: https://issues.apache.org/jira/browse/DERBY-3560
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.3.2.2
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.2.2
>
> Attachments: derby-3560_diff.txt
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3560) build failure: Error running
${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3560:
----------------------------------
Fix Version/s: 10.3.2.2
> build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3560
> URL: https://issues.apache.org/jira/browse/DERBY-3560
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.3.2.2
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.2.2
>
> Attachments: derby-3560_diff.txt
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3560) build failure: Error running
${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3560:
----------------------------------
Attachment: derby-3560_diff.txt
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.
> build failure: Error running ${jdk16}/bin/javac compiler if jdk16 is not set on 10.3
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3560
> URL: https://issues.apache.org/jira/browse/DERBY-3560
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.3.2.2
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3560_diff.txt
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.