db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1031) Test loading derby in a custom ClassLoader
Date Thu, 17 Feb 2011 21:32:12 GMT

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

Myrna van Lunteren updated DERBY-1031:

    Urgency: Normal
     Labels: derby_triage10_8  (was: )

> Test loading derby in a custom ClassLoader
> ------------------------------------------
>                 Key: DERBY-1031
>                 URL: https://issues.apache.org/jira/browse/DERBY-1031
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Kathey Marsden
>              Labels: derby_triage10_8
> Currently we do not test loading Derby in a custom ClassLoader, but actually a lot of
users do actually need this functionality and are using it.   There have been several issues
that have been filed by users surrounding problems with loading Derby in a ClassLoader other
than than just the default classpath loader, for example  DERBY-700, DERBY-668, and DERBY-997.
 It seems clear some testing in this area is needed.
> It would be really nice to have the whole suite run this way and it would also allow
for testing client without the server jars and server without the client jars.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message