[DERBY-4574] derby.jar not a valid R4 OSGi bundle

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.3.0
• Fix Version/s: 10.5.3.1, 10.6.1.0
• Component/s: Services
• Assignee: Bryan Pendleton
• Reporter: Alasdair Nottingham
• Created: 28/Feb/10 15:15
• Updated: 23/May/14 21:15
• Resolved: 13/Jul/10 17:59

Description

The derby.jar has all the bundle metadata you would expect for it to be an OSGi bundle, except for the Bundle-ManifestVersion header. As a result it is not a valid R4 bundle, but will be treated as an R3 bundle.

Looking at the metadata provided it looks as if the bundle should be an R4 bundle. Adding the following will make it a proper R4 bundle.

Bundle-ManifestVersion: 2

Issue Links

• is related to: DERBY-6586 CLONE - derbyclient.jar conflict with derby.jar on package export, which is problematic on OSGI environment
• is related to: DERBY-3730 Bundle-SymbolicName: needed in Derby manifest for OSGi 4 environment
• is related to: DERBY-4120 derbyclient.jar is not a complete OSGi bundle
• is related to: DERBY-1945 Need changes to manifest for OSGi environment
• is required by: DERBY-4728 10.5 backport effort tracking issue