Hi, Myrna, no, I didn't check with jdk14, I didn't know this hierarchy
existed.
I'll retest on jdk14... Just when I thought I had fixed this :)
I can relocate the jdk13-specific canons to the top-level, and stay
consistent with the existing approach.
Boy, I'm glad someone around here knows how this all works :)
David
Myrna van Lunteren wrote:
On 2/2/06, *David Van Couvering (JIRA)* <[email protected]
<mailto:[email protected]>> wrote:
[ http://issues.apache.org/jira/browse/DERBY-905?page=all
<http://issues.apache.org/jira/browse/DERBY-905?page=all> ]
David Van Couvering resolved DERBY-905:
---------------------------------------
Resolution: Fixed
Committed revision 374550
David, I didn't check, but as far as I know the canon system 'builds' on
earlier versions.
Thus, if you check in jdk13 canons, those also get picked up by jdk14 etc.
You'd need another canon for jdk14. I think.
(In fact, normally, we'd put the jdk131 canon at the top level (i.e.
DerbyNetClient, in this case) and then add a jdk14 canon.
Did you re-verify with jdk14?
Thx,
Myrna
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
