[
https://issues.apache.org/jira/browse/DERBY-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632387#action_12632387
]
Myrna van Lunteren commented on DERBY-3782:
-------------------------------------------
After playing with this for a while, I realized that even when we don't need
the services.info.JVMInfo from the Configuration class, it's still getting
included in derbyclient.jar because it's used in the sysinfo calls from the
client.
I personally like approach a better, for otherwise, we get 2 JVMInfo classes in
derbyclient.jar.
But, as the JVMInfo class is getting included anyway, maybe we should not fix
this issue.
Or is there a better approach to addressing this?
> 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
> Attachments: DERBY-3782_a.diff, DERBY-3782_b.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.
