db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2289) Add jdk 1.6 support to jdbcapi tests.
Date Tue, 06 Feb 2007 14:40:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470598

Daniel John Debrunner commented on DERBY-2289:

Using the constant from org.apache.derby.shared.common.reference.JDBC40Translation is the
correct approach.

Compiling with jdk16 means the test will only run under Java SE 6, but this test needs to
run under other jvms. This is because the class file has a version number not understood by
non-Java SE6 vms.
At least that's how it works for the tests in jdbc40.

> Add jdk 1.6 support to jdbcapi tests.
> -------------------------------------
>                 Key: DERBY-2289
>                 URL: https://issues.apache.org/jira/browse/DERBY-2289
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Saurabh Vyas
>         Attachments: Derby-2289_v1.diff, Derby-2289_v1.stat
> Currently jdbcapi test are only dependent on jdk 1.3 & jdk 1.4. But to have support
for testing XML data type, it requires support of jdk 1.6 also (as SQLXML data type is defined
only in jdk 1.6)

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

View raw message