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-2862) ParameterMetaDataJdbc30 fails for weme6.1, which prevents rest of suites.All from completing.
Date Fri, 22 Jun 2007 17:40:26 GMT

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

Daniel John Debrunner commented on DERBY-2862:
----------------------------------------------

java.sql.ParameterMetaData  is not part of JSR 169 thus I assume the test has no meaning for
that environment.

> ParameterMetaDataJdbc30 fails for weme6.1, which prevents rest of suites.All from completing.
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2862
>                 URL: https://issues.apache.org/jira/browse/DERBY-2862
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>            Reporter: A B
>
> With the addtion of the ParameterMetaDataJdbc30 JUnit test (DERBY-2658), suites.All has
been failing with weme6.1. It turns out the that new ParameterMetaDataJdbc30Test fails with
the following error:
>   Failed to invoke suite():java.lang.NoClassDefFoundError: java.sql.ParameterMetaData

> which prevents suites.All from continuing and thus no results can be gathered.
> It might be good to disable the test for weme6.1 at least in the short term so that rest
of suites.All can run cleanly again.  Not sure if that's a complete solution or just a temporary
one until the test can be fixed...

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