db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5810) Include emma.jar on classpath when running compatibility test with instrumented jars
Date Tue, 12 Jun 2012 13:03:43 GMT

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

Knut Anders Hatlen updated DERBY-5810:

    Attachment: d5810-1a.diff

The attached patch is built on top of the 1a patch attached to DERBY-5808. It modifies BaseTestCase.execJavaCmd()
so that it adds emma.jar to the classpath of the sub-processes when running with instrumented

This isn't needed for most callers of execJavaCmd(), as they typically inherit the classpath
from the parent process, which already contains emma.jar. The compatibility tests are a bit
different, as they set the classpath of their sub-processes explicitly in order to be able
to mix and match the different versions.

The compatibility tests ran successfully with instrumented jars when this patch, and the one
for DERBY-5808, were applied.
> Include emma.jar on classpath when running compatibility test with instrumented jars
> ------------------------------------------------------------------------------------
>                 Key: DERBY-5810
>                 URL: https://issues.apache.org/jira/browse/DERBY-5810
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d5810-1a.diff
> When running the compatibility test with EMMA instrumented jars, it fails because it
starts sub-processes without putting emma.jar on their classpath. We should make it construct
a working classpath for its sub-processes if it detects that it's running with instrumented
> This will be easier to fix once DERBY-5808 is checked in.

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


View raw message