[
https://issues.apache.org/jira/browse/DERBY-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009060#comment-14009060
]
Dyre Tjeldvoll commented on DERBY-6586:
---------------------------------------
I think it shows up as resolved because you made it a clone of DERBY-4120.
Which it probably isn't - that issue was about derby client.jar not being a
valid bundle. That was fixed by Bryan's patch which was committed and the
back-ported. That's why DERBY-4120 is marked as resolved. I think it would be
better to track this conflict-issue separately.
And I think the discussion shows that Derby community will need a patch from
someone who actually uses OSGI bundles.
> 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
> Assignee: Bryan Pendleton
>
> 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)
