db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3425) J2EEDataSourceTest throws away stack trace for many errors
Date Sat, 16 Feb 2008 17:13:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Knut Anders Hatlen updated DERBY-3425:

    Attachment: stack.diff

The attached patch changes the test so that the stack traces are preserved.

> J2EEDataSourceTest throws away stack trace for many errors
> ----------------------------------------------------------
>                 Key: DERBY-3425
>                 URL: https://issues.apache.org/jira/browse/DERBY-3425
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: stack.diff
> Many of the test cases in J2EEDataSourceTest call fail() from within a catch block. Instead,
they should just let the exception be thrown and let JUnit handle it. This way the stack trace
will be preserved.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message