Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49791 invoked from network); 18 Sep 2008 21:43:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Sep 2008 21:43:05 -0000 Received: (qmail 28847 invoked by uid 500); 18 Sep 2008 21:43:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 28808 invoked by uid 500); 18 Sep 2008 21:43:01 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 28797 invoked by uid 99); 18 Sep 2008 21:43:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2008 14:43:01 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2008 21:42:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 41B49234C1D9 for ; Thu, 18 Sep 2008 14:42:44 -0700 (PDT) Message-ID: <155230038.1221774164267.JavaMail.jira@brutus> Date: Thu, 18 Sep 2008 14:42:44 -0700 (PDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3782) Client Configuration.java imports engine class org.apache.derby.iapi.services.info.JVMInfo In-Reply-To: <986537469.1216147411741.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632402#action_12632402 ] Kathey Marsden commented on DERBY-3782: --------------------------------------- Option c might be to use reflection to determine if one of the JDBC 4.0 methods exists, so that the JVM version information is not needed. I see what you mean though about there already being a problem with JVMInfo and sysinfo and maybe this is not worth fixing because of that. I guess I don't have a strong opinion. > 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.