Bundle-SymbolicName: needed in Derby manifest for OSGi 4 environment

• Key: DERBY-3730
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Mike Matrigali
• Reporter: Stan Bradbury
• Component/s: Build tools
• Affects Version/s: 10.2.2.0, 10.3.3.0, 10.4.1.3
• Fix Version/s: 10.3.3.1, 10.4.2.0, 10.5.1.1

Description

The manifest does not have a Bundle Symbolic Name. This causes some tools not to recognize it as an OSGi bundle and some things don't work nicely without the symbolic name.
Add Bundle-SymbolicName: derby to the manifest.

NOTE: this issue will address issue #1 of the multi-issue bug: DERBY-1945

Comments

[Andrew McIntyre]

Attaching a patch which sets Bundle-SymbolicName. Is this all that is needed for this issue?

[Manjula Kutty]

Thanks for the patch Andrew. I applied the patch and built derby.jar and now there is an entry for the Bundle-SymbolicName with the value derby on the MANIFEST file

[Stan Bradbury]

Hi Manjula and OSGI advocates -

I've confirmed that the manifest in the sample build created with this patch meets the needs for use in an OSGI 4 bundle. Please commit to the codeline and backport to at least v 10.3. Thanks for the prompt turnaound : ) .

[Mike Matrigali]

I'll take care of committing and apply it to at least trunk, 10.4, and 10.3.

[Mike Matrigali]

Fix has been applied to trunk, 10.4 branch and 10.3 branch.