[
https://issues.apache.org/jira/browse/DERBY-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600895#action_12600895
]
Kathey Marsden commented on DERBY-3618:
---------------------------------------
I wonder what the status is on sharing classes between jars. There were
conversations long ago about the problems this could cause if there were mixed
version jars in the classpath, which I don't think were resolved. Is it ok
for SanityManager classes because they are only for sane builds. I also
thought that in general the testing code was not supposed to use any product
code. Even though it's duplicate code. I think I would prefer the testing code
be kept separate.
> 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
>
>
> 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.
