db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: [jira] Resolved: (DERBY-905) derbyall nightly failure in LOBTest running under DerbyNetClient - jdk131 specific
Date Fri, 03 Feb 2006 01:13:56 GMT
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)* <derby-dev@db.apache.org 
> <mailto:derby-dev@db.apache.org>> 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
> 
>  

Mime
View raw message