[
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)
