Hi, Knut. I don't know why org.apache.derby.iapi.services.info.JVMInfo
is in derbyclient.jar, this seems like a bug. I agree that what you
have is JVMInfo is getting shared across client and engine, something we
have so far not approved because of the issues around shadowing and
compatibility.
I recommend logging a JIRA item, and that we try and track this down.
David
Knut Anders Hatlen wrote:
"David W. Van Couvering" <[EMAIL PROTECTED]> writes:
Knut Anders Hatlen wrote:
I just noticed that JVMInfo is included twice in derbyclient.jar. Does
anyone know if this is intended?
% jar tf derby.jar|grep JVMInfo
org/apache/derby/iapi/services/info/JVMInfo.class
% jar tf derbyclient.jar|grep JVMInfo
org/apache/derby/iapi/services/info/JVMInfo.class
org/apache/derby/shared/common/info/JVMInfo.class
Yes, I had to make a copy to make use of it in the client code.
I might be missing something, but it seems like
org.apache.derby.shared.common.info.JVMInfo is the only one of them
that is used in the client code. Why must
org.apache.derby.iapi.services.info.JVMInfo be in derbyclient.jar?
Couldn't this cause problems for embedded if an older version
derbyclient.jar is before derby.jar in the classpath?
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
