Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <189673489.1246405127637.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 16:38:47 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1031) Test loading derby in a custom
 ClassLoader
In-Reply-To: <1649414046.1140638499307.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dag H. Wanvik updated DERBY-1031:
---------------------------------

    Issue Type: Improvement  (was: Test)

> 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: 10.2.1.6
>            Reporter: Kathey Marsden
>
> 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.
-
You can reply to this email to add a comment to the issue online.