Hi,
Absolutely no problem. There was no need to apologise at all. I will take a look at it. Although I really don't know how much insight I can provide.
thanx,
Narayanan

Andrew McIntyre wrote:
On 8/2/06, Narayanan <[EMAIL PROTECTED]> wrote:
Hi,
The subject of the email said JUnit. The TestConnectionMethods.java is
not a JUnit test.

My mistake, sorry. I incorrectly assumed that all of the jdbc4 tests
were junit tests. Anyway, I suppose I'll look at instrumenting this
test to return full stack traces. Any insight anyone can provide as to
why this would fail with the patch attached to DERBY-1424 that only
removes unnecessary classes from derbyclient.jar is still greatly
appreciated.

Thanks,
andrew

Reply via email to