db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-4689) Provide a JUnit test option to isolate client from server jars in a separate class loader to expose any dependencies that may exist
Date Thu, 28 Oct 2010 21:13:24 GMT

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

Lily Wei reassigned DERBY-4689:
-------------------------------

    Assignee: Lily Wei

> Provide a JUnit test option to isolate client from server jars in a separate class loader
to expose any dependencies that may exist
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4689
>                 URL: https://issues.apache.org/jira/browse/DERBY-4689
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.7.1.0
>            Reporter: Kathey Marsden
>            Assignee: Lily Wei
>         Attachments: derby-4689-01.diff
>
>
> Client programs should be able to run without derby.jar or derbynet.jar in the classpath.
 It would be great to have a test option, e.g. derby.tests.isolateServer which isolates derbynet.jar
and derby.jar from derbyclient.jar,  derbytools.jar and derbyTesting.jar to verify this. One
recent issue that was discovered and not caught by the tests was DERBY-4688.  

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