Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 23 May 2014 21:17:02 +0000 (UTC)
From: "Charlie Mordant (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12716443.1400879745859.11498.1400879821997@arcas>
In-Reply-To: <JIRA.12716443.1400879745859@arcas>
References: <JIRA.12716443.1400879745859@arcas>
Subject: [jira] [Created] (DERBY-6586) CLONE - derbyclient.jar conflict with
 derby.jar on package export, which is problematic on OSGI environment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Charlie Mordant created DERBY-6586:
--------------------------------------

             Summary: CLONE - derbyclient.jar conflict with derby.jar on package export, which is problematic on OSGI environment
                 Key: DERBY-6586
                 URL: https://issues.apache.org/jira/browse/DERBY-6586
             Project: Derby
          Issue Type: Bug
          Components: Eclipse Plug-in, Services
    Affects Versions: 10.4.2.0
         Environment: OSGi
            Reporter: Charlie Mordant
            Assignee: Bryan Pendleton
             Fix For: 10.5.3.1, 10.6.1.0


The manifest in derbyclient.jar is incomplete for usage in OSGi.  There are no packages exported.  This appears to only be a problem in standalone equinox (outside of eclipse).  Note that I did not try other OSGi containers.

The fix is relatively simple.  Adding the Export-Package manifest header should take care of the problem.


--
This message was sent by Atlassian JIRA
(v6.2#6252)