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.
David
Andrew McIntyre wrote:
On 3/13/06, David W. Van Couvering <[EMAIL PROTECTED]> 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
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
