[
https://issues.apache.org/jira/browse/DERBY-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4689:
----------------------------
Assignee: (was: Lily Wei)
Labels: derby_triage10_8 (was: )
Currently not working on this issue. Unassigned myself.
> 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.1
> Reporter: Kathey Marsden
> Labels: derby_triage10_8
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
