db-derby-dev mailing list archives

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

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

Saurabh Vyas updated DERBY-2289:
--------------------------------

    Derby Info: [Patch Available]

Dan I tried your approach also now, that works fine as SQLXML constant can be picked from
org.apache.derby.shared.common.reference.JDBC40Translation.

So which approach should be followed?
If we use this than this issue can be marked invalid as we than need not change anything in
the build.xml to provide support for jdk 1.6

> 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.


Mime
View raw message