[
https://issues.apache.org/jira/browse/DERBY-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erlend Birkenes updated DERBY-3618:
-----------------------------------
Attachment: DERBY-3618_4.diff
Version 4.
Fixed a problem in the last patch where a reference to ThreadDump caused the
build to fail. This was to get it added to the jars, but this is now properly
done by adding it to dnc.properties and extraDBMSclasses.properties.
But there is still a problem. I'm getting:
[javac]
/home/erlend/workspace/Derby/java/shared/org/apache/derby/shared/common/sanity/AssertFailure.java:32:
package org.apache.derby.iapi.services.info does not exist
[javac] import org.apache.derby.iapi.services.info.JVMInfo;
[javac] ^
[javac]
/home/erlend/workspace/Derby/java/shared/org/apache/derby/shared/common/sanity/AssertFailure.java:33:
package org.apache.derby.iapi.services.monitor does not exist
[javac] import org.apache.derby.iapi.services.monitor.Monitor;
This packages are compiled after org/apache/derby/shared/ as part if the engine
target, which is depending on the shared target.
How can I fix this?
-Erlend
> Perform thread dump with ASSERTS with jdk 1.5 or higher
> -------------------------------------------------------
>
> Key: DERBY-3618
> URL: https://issues.apache.org/jira/browse/DERBY-3618
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Erlend Birkenes
> Priority: Minor
> Attachments: DERBY-3618_1.diff, DERBY-3618_2.diff, DERBY-3618_3.diff,
> DERBY-3618_4.diff
>
>
> It would be good to have a stack traces for all threads dump to the derby.log
> when an assertion occurs with JVM's that support it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
