[ http://issues.apache.org/jira/browse/DERBY-819?page=comments#action_12363205 ]
Daniel John Debrunner commented on DERBY-819: --------------------------------------------- Index: java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestException_app.properties =================================================================== --- java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestException_app.properties (revision 0) +++ java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestException_app.properties (revision 0) @@ -0,0 +1,6 @@ +runwithibm13=false +runwithibm14=false +runwithj9=false +runwithjdk12=false +runwithjdk13=false +runwithjdk14=false I would strongly encourage always commenting *why* a test is excluded. Especially in this case if the test retains its generic name. The reason the test is excluded may look obvious now, but may not two, five etc. years from now. It's a good habit to get into. > Provide JDBC4 SQLException subclasses support in Embedded driver > ---------------------------------------------------------------- > > Key: DERBY-819 > URL: http://issues.apache.org/jira/browse/DERBY-819 > Project: Derby > Type: Sub-task > Components: JDBC > Environment: all > Reporter: Anurag Shekhar > Assignee: Anurag Shekhar > Priority: Minor > Attachments: derby-819.diff, stat.out > -- 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
