Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13306593.162891278021657141.JavaMail.jira@thor>
Date: Thu, 1 Jul 2010 18:00:57 -0400 (EDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Reopened: (DERBY-4574) derby.jar not a valid R4 OSGi bundle
In-Reply-To: <1327816601.20491267370225793.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden reopened DERBY-4574:
-----------------------------------


reopen for 10.5 back port

> 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.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.