Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 712911841F for ; Sun, 6 Mar 2016 00:04:41 +0000 (UTC) Received: (qmail 14704 invoked by uid 500); 6 Mar 2016 00:04:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 14665 invoked by uid 500); 6 Mar 2016 00:04:41 -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 14619 invoked by uid 99); 6 Mar 2016 00:04:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Mar 2016 00:04:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0EF662C1F58 for ; Sun, 6 Mar 2016 00:04:41 +0000 (UTC) Date: Sun, 6 Mar 2016 00:04:41 +0000 (UTC) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6586) CLONE - derbyclient.jar conflict with derby.jar on package export, which is problematic on OSGI environment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181915#comment-15181915 ] Bryan Pendleton commented on DERBY-6586: ---------------------------------------- Ah. somehow I had missed the fact that this issue involved the "Embedded Server" configuration, in which a single JVM hosts both the server(+engine) as well as the client. Yes, I can see that this would be problematic if you are using a runtime system that enforces that certain packages come only from a single jar. > CLONE - derbyclient.jar conflict with derby.jar on package export, which is problematic on OSGI environment > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-6586 > URL: https://issues.apache.org/jira/browse/DERBY-6586 > Project: Derby > Issue Type: Bug > Components: Network Client, Network Server > Affects Versions: 10.10.2.0 > Environment: OSGi > Reporter: Charlie Mordant > > The manifest in derbyclient.jar is incomplete for usage in OSGi. There are no packages exported. This appears to only be a problem in standalone equinox (outside of eclipse). Note that I did not try other OSGi containers. > The fix is relatively simple. Adding the Export-Package manifest header should take care of the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)