Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3782

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

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.5.1.1
    • Fix Version/s: 10.5.1.1
    • Component/s: Network Client
    • Labels:
      None
    • Issue & fix info:
      High Value Fix

      Description

      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.

        Attachments

        1. DERBY-3782_c.diff
          1.0 kB
          Myrna van Lunteren
        2. DERBY-3782_b.diff
          6 kB
          Myrna van Lunteren
        3. DERBY-3782_a.diff
          4 kB
          Myrna van Lunteren

          Activity

            People

            • Assignee:
              myrna Myrna van Lunteren
              Reporter:
              kmarsden Katherine Marsden

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment