[
https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769009#action_12769009
]
Bryan Pendleton commented on DERBY-4120:
----------------------------------------
After reading through the papers a bit, and looking at the actual contents of
derbyclient.jar,
it seems to me that the only thing we should put into the Manifest for
derbyclient.jar is:
Export-Package: org.apache.derby.jdbc
I think that all the other packages in derbyclient.jar are internal, and the
only externally-visible
package should be the above package, which contains ClientDriver.class
I'll try that change, as it is the smallest and most focused.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
