[DERBY-4120] derbyclient.jar is not a complete OSGi bundle

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.2.0
• Fix Version/s: 10.5.3.1, 10.6.1.0
• Component/s: Eclipse Plug-in, Services
• Environment: OSGi
• Urgency: Normal
• Issue & fix info: High Value Fix, Known fix
• Bug behavior facts: Embedded/Client difference
• Assignee: Bryan Pendleton
• Reporter: JJ Snyder
• Created: 26/Mar/09 13:05
• Updated: 21/Jan/15 00:23
• Resolved: 13/Jul/10 17:47

Description

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.

Issue Links

• is cloned by: DERBY-6586 CLONE - derbyclient.jar conflict with derby.jar on package export, which is problematic on OSGI environment
• is required by: DERBY-4728 10.5 backport effort tracking issue
• relates to: DERBY-4574 derby.jar not a valid R4 OSGi bundle