[
https://issues.apache.org/jira/browse/DERBY-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen reassigned DERBY-5821:
-----------------------------------------
Assignee: Knut Anders Hatlen
It's probably better to convert the test to JUnit and leave the old harness as
it is. I'll give it a try.
> tools/derbyrunjartest.java doesn't use jvmflags
> -----------------------------------------------
>
> Key: DERBY-5821
> URL: https://issues.apache.org/jira/browse/DERBY-5821
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
>
> tools/derbyrunjartest.java doesn't use the jvmflags property when it starts a
> sub-process, so one cannot pass custom flags to the process. This makes it
> difficult to get the test to pass when running with code coverage tools.
> For example, for EMMA, we need to manipulate the classpath and reduce the
> verbosity level. And we need to pass a -javaagent flag if we're running with
> JaCoCo. Using the jvmflags property works for those tests that don't spawn
> processes.
--
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
