[ http://issues.apache.org/jira/browse/DERBY-1133?page=all ]
Rick Hillegas updated DERBY-1133:
---------------------------------
Attachment: bug1133_rev2.diff
Hi Kristian,
Thanks for reviewing this patch. Here are responses to your review:
1) No good reason. I just didn't know about DerbyNetClient.exclude. Thanks for
teaching me about this corner of our test harness fractal. I have eliminated
the useless jdbc40_embeddedOnly suite and attached a second rev of the patch.
This is much better.
2) I think Myrna answered this question affirmatively on derby-dev.
3) I agree that we want to wire jdbc40 into derbyall and derbynetclientmats
once Anurag finishes work on DERBY-955.
> Split jdbc4 tests so that the suite can be run independently under the
> embedded and DerbyNetClients like other Derby test suites
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1133
> URL: http://issues.apache.org/jira/browse/DERBY-1133
> Project: Derby
> Type: Improvement
> Components: Test
> Versions: 10.2.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: bug1133.diff, bug1133_rev2.diff
>
> Right now the jdbc4 suite runs under the DerbyNetClient. However, under the
> covers, the tests also run themselves against the embedded client. We should
> fix these tests so that the whole suite can run just under DerbyNetClient or
> just under the embedded client.
--
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
