You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2009/11/21 22:42:39 UTC

[jira] Resolved: (DERBY-2024) Remove JUnit utility method JDBC.vmSupportsJDBC2

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

Bryan Pendleton resolved DERBY-2024.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0

Thanks Knut for having a look at the patch. Committed to the trunk as revision 883000.

Please keep your eyes out for any new test behaviors, particularly in JSR169 configurations.

> Remove JUnit utility method JDBC.vmSupportsJDBC2
> ------------------------------------------------
>
>                 Key: DERBY-2024
>                 URL: https://issues.apache.org/jira/browse/DERBY-2024
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Daniel John Debrunner
>            Assignee: Bryan Pendleton
>             Fix For: 10.6.0.0
>
>         Attachments: removeFunction.diff
>
>
> Replace its use with vmSupportsJDBC3() when required or modify the checks to work upon the assumption that JDBC3/JSR169 is the base level (e..g holdability is always supported).

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