[jira] [Updated] (DERBY-5808) Compatibility test should use BaseTestCase.execJavaCmd()

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen updated DERBY-5808:
--------------------------------------

    Attachment: d5808-1a.diff

The attached patch (d5808-1a.diff) makes the following changes:

- junit/BaseTestCase.java:

Make it possible to specify which Java executable to use when invoking execJavaCmd() (since the compatibility test mixes multiple Java versions).

- functionTests/tests/replicationTests/ReplicationRun.java:

Update call to execJavaCmd() to match the new signature.

- functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java:

Replace all calls to Runtime.exec() with calls to BaseTestCase.execJavaCmd().

I ran derbyall + suites.All + compatibility test successfully with the patch.
                
> Compatibility test should use BaseTestCase.execJavaCmd()
> --------------------------------------------------------
>
>                 Key: DERBY-5808
>                 URL: https://issues.apache.org/jira/browse/DERBY-5808
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.10.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5808-1a.diff
>
>
> The compatibility test should use BaseTestCase.execJavaCmd() instead of calling Runtime.exec() directly. This would make it easier to pass flags (like EMMA code coverage properties) to the processes spawned by the compatibility test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira