[
https://issues.apache.org/jira/browse/DERBY-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887838#action_12887838
]
Myrna van Lunteren commented on DERBY-4574:
-------------------------------------------
I was contemplating this backport, but I think DERBY-4120 also should get
backported. That would make the 10.6 and 10.5 build.xml files look similar with
regards to OSGI elements.
I already re-assigned this one, and will do the same for DERBY-4120, hope
that's OK.
I could not come up with any useful automated test, and I guess no one did when
the fix went in originally. If a test can be devised, it would merit a separate
issue (and backport).
> derby.jar not a valid R4 OSGi bundle
> ------------------------------------
>
> Key: DERBY-4574
> URL: https://issues.apache.org/jira/browse/DERBY-4574
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.3.0
> Reporter: Alasdair Nottingham
> Assignee: Myrna van Lunteren
> Fix For: 10.6.1.0
>
> Attachments: addBundleManifestVersion.diff
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
