db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-3782) Client Configuration.java imports engine class org.apache.derby.iapi.services.info.JVMInfo
Date Mon, 22 Sep 2008 16:56:44 GMT

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

Myrna van Lunteren resolved DERBY-3782.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0
         Assignee: Myrna van Lunteren

I committed patch _c with revision 697897.
Note, that as indicated before, JVMInfo still is part of derbyclient.jar (I assume because
of the need to support sysinfo).

> Client Configuration.java imports engine class  org.apache.derby.iapi.services.info.JVMInfo

> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3782
>                 URL: https://issues.apache.org/jira/browse/DERBY-3782
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.5.0.0
>
>         Attachments: DERBY-3782_a.diff, DERBY-3782_b.diff, DERBY-3782_c.diff
>
>
> The client code (org.apache.derby.client.am.Configuration) imports the engine class org.apache.derby.iapi.services.info.JVMInfo.
> This will make two copies of the class in derby.jar and derbyclient.jar which can cause
problems if mixed version jars are used and  I think may cause jar sealing issues as well.
> Until we have a good framework for sharing code between engine and client, the client
shouldn't import engine classes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message