You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2016/03/05 17:51:40 UTC
[jira] [Updated] (DERBY-6586) CLONE - derbyclient.jar conflict with
derby.jar on package export, which is problematic on OSGI environment
[ https://issues.apache.org/jira/browse/DERBY-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Pendleton updated DERBY-6586:
-----------------------------------
Assignee: (was: Bryan Pendleton)
> 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)