[
https://issues.apache.org/jira/browse/DERBY-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-3763.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
10.4.1.4
Derby Info: (was: [Patch Available])
My test runs passed with patch 1b applied.
Committed 'derby-3763-1b-usingDB2Client.diff' to trunk with revision 677848.
Backported to 10.4 with revision 677849.
> Rename BaseJDBCTestCase.usingDerbyNet
> -------------------------------------
>
> Key: DERBY-3763
> URL: https://issues.apache.org/jira/browse/DERBY-3763
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.1.4, 10.5.0.0
>
> Attachments: derby-3763-1a-usingDB2Client.diff,
> derby-3763-1a-usingDB2Client.stat, derby-3763-1b-usingDB2Client.diff,
> derby-3763-1b-usingDB2Client.stat
>
>
> The names of the methods 'usingDerbyNet' and 'usingDerbyNetClient' in
> BaseJDBCTestCase are confusing.
> I propose we change the one used to tell if we are using the DB2 client
> driver (JCC).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
