Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 23 May 2014 21:15:03 +0000 (UTC)
From: "Charlie Mordant (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12419485.1238072723238.11496.1400879703317@arcas>
In-Reply-To: <JIRA.12419485.1238072723238@arcas>
References: <JIRA.12419485.1238072723238@arcas>
Subject: [jira] [Commented] (DERBY-4120) derbyclient.jar is not a complete
 OSGi bundle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007711#comment-14007711 ] 

Charlie Mordant commented on DERBY-4120:
----------------------------------------

Why is it resolved?

It's not resolved at all! derby.jar and derbyclient.jar are both exporting org.apache.derby.jdbc package, thus make it impossible to have a derby db and a client on the same OSGI runtime...


> derbyclient.jar is not a complete OSGi bundle
> ---------------------------------------------
>
>                 Key: DERBY-4120
>                 URL: https://issues.apache.org/jira/browse/DERBY-4120
>             Project: Derby
>          Issue Type: Bug
>          Components: Eclipse Plug-in, Services
>    Affects Versions: 10.4.2.0
>         Environment: OSGi
>            Reporter: JJ Snyder
>            Assignee: Bryan Pendleton
>             Fix For: 10.5.3.1, 10.6.1.0
>
>         Attachments: addToManifest.diff
>
>
> 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.2#6252)