[
https://issues.apache.org/jira/browse/DERBY-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009683#comment-14009683
]
Christian Schneider commented on DERBY-4120:
--------------------------------------------
If I understand correctly the issue is that derby and derby client have the
package org.apache.derby.jdbc with different contents. This does not work in
OSGi. So the first step should be to move the code to different packages. The
client jar seems to contain less packages so it is probably easer to move these.
If you want to stay compatible you could create a new package
org.apache.derby.client.jdbc and copy the classes there while keeping them in
the original place too with @Deprecated to mark that people should switch. Then
you could only export the new package in the Manifest. So OSGi users can/have
to use the new packages while other users have some time to switch until the
next major version where you could remove the old package.
Another option would be to add the client classes into the derby jar so people
can simply either install derby or client and do not need both.
What do you think?
> 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, derby OSGI issue.jpg
>
>
> 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)
