Hi, the two finally blocks are intentional. As per Knut's suggestion I added it so that if some how copying the derby.log fails , we will not loose the original exception.
On 2/22/08, Myrna van Lunteren (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571549#action_12571549] > > Myrna van Lunteren commented on DERBY-2667: > ------------------------------------------- > > I did not notice the weird spacing before committing, sorry... > I wanted to fix it and noticed I had missed another issue - we now have > two finally blocks, one of which will never be reached... > > > Create more robust junit TestRunner for running derby tests > > ------------------------------------------------------------ > > > > Key: DERBY-2667 > > URL: https://issues.apache.org/jira/browse/DERBY-2667 > > Project: Derby > > Issue Type: Improvement > > Components: Test > > Affects Versions: 10.3.1.4 > > Reporter: Kathey Marsden > > Priority: Minor > > Attachments: DERBY-2667_diff_02_06.txt, > DERBY-2667_diff_02_15.txt, DERBY-2667_diff_02_21.txt, > DERBY-2667_diff_2_19.txt, DERBY-2667_stat_02_06.txt, > DERBY-2667_stat_02_15.txt, DERBY-2667_stat_02_19.txt, > DERBY-2667_stat_02_21.txt, JUnitMethodTrace.diff.txt, > JUnitMethodTrace_Extra.diff.txt, MemRunner.java, TimeRunner.java > > > > > > Provide a more full featured TestRunner for Derby testing. > > junit.textui.TestRunner is not very robust. It does not for example > print the tests as they run or print chained exceptions, create separate > files for the full report and just failures. It would be great to have a > standardized TestRunner that everyone uses. Perhaps someone already has one > that they would like to contribute as a starter. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Thanks, Manjula.
