You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/15 20:45:31 UTC

[jira] Updated: (DERBY-3782) Client Configuration.java imports engine class org.apache.derby.iapi.services.info.JVMInfo

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

Kathey Marsden updated DERBY-3782:
----------------------------------

    Summary: Client Configuration.java imports engine class  org.apache.derby.iapi.services.info.JVMInfo   (was: Client Configuration.java imports engine file import org.apache.derby.iapi.services.info.JVMInfo )

> 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
>            Priority: Minor
>
> 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.