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:11:05 GMT

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

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

    Attachment: Derby-2289_v1.stat
                Derby-2289_v1.diff

Modified build.xml in jdbcapi tests to add another compile target which uses jdk 1.6.
Removed DatabaseMetaDataTest from compile target which uses jdk 1.4, thus DatabaseMetaDataTest
will now be compiled against jdk 1.6 and will have SQLXML data type available.

Is this approach correct?

> 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