You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2010/07/13 20:01:50 UTC
[jira] Resolved: (DERBY-4574) derby.jar not a valid R4 OSGi bundle
[ https://issues.apache.org/jira/browse/DERBY-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-4574.
---------------------------------------
Assignee: Bryan Pendleton (was: Myrna van Lunteren)
Fix Version/s: 10.5.3.1
Resolution: Fixed
merged to 10.5 with revision 963799.
svn merge command: svn merge -c 918152 https://svn.apache.org/repos/asf/db/derby/code/trunk
I verified that appropriate entries are in the META-INF/MANIFEST.MF file in derby.jar and derbyclient.jar.
> 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: Bryan Pendleton
> Fix For: 10.5.3.1, 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.