You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Matthew T. Adams (JIRA)" <ji...@apache.org> on 2011/08/30 21:15:39 UTC
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in
manifest to include version
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094013#comment-13094013 ]
Matthew T. Adams commented on JDO-684:
--------------------------------------
It looks like this has already been fixed in the trunk for JDO 3.1.
> Fix OSGi Export-Package entries in 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
> Labels: export-package, jdo, osgi
> 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