[
https://issues.apache.org/jira/browse/DERBY-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre updated DERBY-2505:
-----------------------------------
Attachment: derby-2505-jarfix.diff
Attaching a patch which fixes the problem running the test with jars. Moves
writing ij's output into the extinout directory, and then grants permission to
read/write/delete from ${user.dir}/extinout to derbytools.jar
> Convert derbynet/testij.java to JUnit
> -------------------------------------
>
> Key: DERBY-2505
> URL: https://issues.apache.org/jira/browse/DERBY-2505
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Reporter: Andrew McIntyre
> Assigned To: Andrew McIntyre
> Priority: Minor
> Attachments: derby-2505-jarfix.diff, derby-2505-v1.diff
>
>
> In the process of converting this test, I realized we needed an way to run ij
> tests that would work with multiple connections. So, I made an IjTestCase
> that runs a script through ij's main method, redirects the output to a file,
> and then compares the file to a canon.
> Attaching a patch for this issue which does that. The test creates several
> databases during its run. Should the JUnit wrappers for ij tests be cleaning
> these up, or will these get cleaned up later automatically?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
