JVMInfo included twice in derbyclient.jar

[Knut Anders Hatlen <Kn...@Sun.COM>]

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

-- 
Knut Anders

Re: JVMInfo included twice in derbyclient.jar

["David W. Van Couvering" <Da...@Sun.COM>]

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" <Da...@Sun.COM> 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?
> 

Re: JVMInfo included twice in derbyclient.jar

[Knut Anders Hatlen <Kn...@Sun.COM>]

"David W. Van Couvering" <Da...@Sun.COM> 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?

-- 
Knut Anders

Re: JVMInfo included twice in derbyclient.jar

["David W. Van Couvering" <Da...@Sun.COM>]

Yes, I had to make a copy to make use of it in the client code.

David

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
>