[
https://issues.apache.org/jira/browse/DERBY-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-3782:
--------------------------------------
Attachment: DERBY-3782_c.diff
I'm attaching a third patch that uses the same check as the tests to identify
if we've got JDBC 4 support or not.
It seemed to work ok - I ran suites.All with only a replication test failure
with jdk15, and no failures with jdk16.
I'm inclined to commit this, and close this issue (leaving the sysinfo/JVMInfo
issue untouched).
> 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, 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.
