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: SanityManager in shared package
Date Tue, 14 Mar 2006 01:01:13 GMT
OK, sounds good.  I can't see what the issue would be either, since 
compatibility is only an issue for released jars.

I am *hoping* to get this solved soon, but I have higher priority itches 
to scratch right now.


Andrew McIntyre wrote:
> On 3/13/06, David W. Van Couvering <David.Vancouvering@sun.com> wrote:
>>I'd like to use SanityManager in the 'shared' package hierarchy.
>>- Put into the shared package and have both engine and client jar files
>>pick up the same class.  This is basically shared code, and comes with
>>the related potential shadowing issues.  But perhaps SanityManager is
>>stable enough this is not an issue?
>>What are your thoughts on this?
> Well, since the SanityManager isn't included in the insane jars, thus
> not included in the public releases, and isn't used in the client at
> all, I wouldn't think it would be a problem to just move it over. You
> might want to get a second opinion on that, though.
> andrew

View raw message