db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3763) Rename BaseJDBCTestCase.usingDerbyNet
Date Thu, 17 Jul 2008 16:29:31 GMT

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

Kristian Waagan updated DERBY-3763:
-----------------------------------

    Attachment: derby-3763-1b-usingDB2Client.stat
                derby-3763-1b-usingDB2Client.diff

Patch 1b changes some additional comments as suggested by Dag and includes an additional change
in JDBCClient.
TestConfiguration is still using the string "DerbyNet" when parsing properties from the old
harness.

suites.All passed, running derbyall.
Plan to commit tomorrow.

> 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
>         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.


Mime
View raw message