You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2015/01/22 23:23:36 UTC

[jira] [Assigned] (DERBY-5219) Make it possible to set the classpath of the Derby tests using the -cp command line arg instead of setting the CLASSPATH environment variable.

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

Myrna van Lunteren reassigned DERBY-5219:
-----------------------------------------

    Assignee:     (was: Jayaram Subramanian)

Unassigning - there has been no activity in a year - maybe someone else is interested in doing this.

> Make it possible to set the classpath of the Derby tests using the -cp command line arg instead of setting the CLASSPATH environment variable.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5219
>                 URL: https://issues.apache.org/jira/browse/DERBY-5219
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.9.1.0
>            Reporter: Rick Hillegas
>
> The instructions for running Derby tests say that you need to set the CLASSPATH environment variable. This rule is described here: http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co#2.1_running_with_derby_classes_ If, instead, you set the classpath using the -cp command line argument, the classpath won't be properly set in the subprocesses which the test harness spawns. It should be possible for the harness to introspect its classpath and pass that information to subprocesses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)