[
https://issues.apache.org/jira/browse/DERBY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114802#comment-13114802
]
Kathey Marsden commented on DERBY-1046:
---------------------------------------
This issue was closed as fixed but the patch was actually not checked in. It
looks like sysinfo does use JVMInfo at least in 10.8, but doesn't need too
really, so perhaps Andrew's solution of excluding JVMInfo is a good one but
some other minor changes to sysinfo would also be needed.
> JVMInfo is duplicated in derbyclient.jar
> ----------------------------------------
>
> Key: DERBY-1046
> URL: https://issues.apache.org/jira/browse/DERBY-1046
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.2.1.6
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.2.1.6
>
> Attachments: derby-1046.diff
>
>
> The JVMInfo class is included twice in derbyclient.jar, as
> org.apache.derby.iapi.services.info.JVMInfo and
> org.apache.derby.shared.common.info.JVMInfo. The only one of them
> actually used by the client code is the one found in
> org.apache.derby.shared.common.info.
> org.apache.derby.iapi.services.info.JVMInfo is also included in
> derby.jar, so one could run into problems if the classpath contains
> derbyclient.jar and derby.jar with different versions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
