[ http://issues.apache.org/jira/browse/DERBY-514?page=comments#action_12372134 ]
Deepa Remesh commented on DERBY-514: ------------------------------------ Rick, Thanks for the suggestion. I have been trying something along similar lines but when I am running the test using the test harness, the test jvm does not see the system properties set on the command-line. I tried using jvmflags to pass in the properties to the test jvm but this allows only 1 property to be passed because of known limitation (DERBY-1091). I think we will have to first extract the location of new jars from the user's classpath (I'm working on this now). Once this is done, I can try to pass in the old jar location in jvmflags property to the test jvm. Your idea of the build script generating a properties file with location of the old jars sounds good. I will think about how to do this. Thanks again for looking into this. Adding the upgrade test to the harness seems to be more involved task than what I expected. So I am planning to break the changes in derby-514-patch1-v1.diff into smaller patches and will attach them. Please note that derby-514-patch1-v1.diff is not ready for commit. However, I would appreciate any other feedback on it. > Integrate upgrade tests into test suite > --------------------------------------- > > Key: DERBY-514 > URL: http://issues.apache.org/jira/browse/DERBY-514 > Project: Derby > Type: Test > Components: Test > Versions: 10.1.2.0, 10.2.0.0 > Reporter: Kathey Marsden > Assignee: Deepa Remesh > Fix For: 10.2.0.0 > Attachments: derby-514-patch1-v1.diff, derby-514-patch1-v1.status > > Currently there are no upgrade tests in the derbyAll suite. > The upgrade tests java/testing/org/apache/derbyTesting are run by script and > require that the version to be tested by specified on the command line so > that the classpath can be changed. > # runphases old_major old_minor old_engine new_engine > # > # e.g. > # > # runphases 10 0 c:/derby/10.0.2.1/lib c:/derby/trunk/jars/sane > Perhaps this script can be rewritten in Java using class loaders and > previous Derby verssions such as 10.0 and 10.1 be checked in so that this > testing can be incorporated into the derbyAll test suite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
