Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Fri, 9 Sep 2011 16:43:09 +0000 (UTC)
From: "Michael Bouschen (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: 
 <1957914103.8773.1315586589107.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <284030444.8858.1314731622008.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (JDO-684) Fix OSGi Export-Package entries in JDO
 3.0 manifest to include version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Bouschen reassigned JDO-684:
------------------------------------

    Assignee: Matthew T. Adams

> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
>                 Key: JDO-684
>                 URL: https://issues.apache.org/jira/browse/JDO-684
>             Project: JDO
>          Issue Type: Bug
>          Components: api
>    Affects Versions: JDO 3
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>              Labels: export-package, jdo, osgi
>             Fix For: JDO 3 update 1
>
>         Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry.  I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published.  Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira