[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371372 ]
Rick Hillegas commented on DERBY-1097: -------------------------------------- I'm afraid I don't know how to wire this test into the jdbc40 suite. I tried wiring StatementTest.junit at the end of the jdbc40 suite but I get the following error under embedded and network: ********* Diff file jdbc40/jdbc40/StatementTest.diff *** Start: StatementTest jdk1.6.0-beta2 jdbc40:jdbc40 2006-03-21 17:27:59 *** 0 add > java.lang.NoSuchMethodError: main > Exception in thread "main" Test Failed. *** End: StatementTest jdk1.6.0-beta2 jdbc40:jdbc40 2006-03-21 17:28:13 *** > Add tests for Statement.isClosed() > ---------------------------------- > > Key: DERBY-1097 > URL: http://issues.apache.org/jira/browse/DERBY-1097 > Project: Derby > Type: Sub-task > Components: Test > Versions: 10.2.0.0 > Environment: JDBC4 / JDK 1.6 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Attachments: DERBY-1097-2a.diff, DERBY-1097-2a.stat, DERBY-1097-2b.diff, > StatementTest.java, StatementTest.java-v1, StatementTestSetup.java, > StatementTestSetup.java-v1 > > Add tests for Statement.isClosed() (implemented as part of DERBY-953). > The tests are already written, but because of some "confusion" and diverging > paths regarding how to get connections when running JUnit tests, they are > held back. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
