db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-1046) JVMInfo is duplicated in derbyclient.jar
Date Tue, 27 Sep 2011 22:14:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-1046:

    Attachment: derby-1046_diff.txt

Attached is a patch for this issue which removes the call to JVMInfo.derbyVMLevel() in tools.sysinfo.Main
and replaces it with a local method.  The new local method is simpler than the initialization
in JVMInfo, but I think it is sufficient for sysinfo.  

I tried sysinfo with the  with IBM and Sun JDK's 1.4.2, 1.5, 1.6, and 1.7 as well as weme
6.2. I verified that it fixes DERBY-5431. I am running tests now.

I would appreciate if someone could try sysinfo with  patch with phoneME and Oracle embedded
ME client.

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Kathey Marsden
>            Priority: Minor
>             Fix For:
>         Attachments: derby-1046.diff, derby-1046_diff.txt
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message