[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094746#comment-13094746
]
Matthew T. Adams commented on JDO-684:
--------------------------------------
Yes, Andy. Exactly like that.
Everyone else: can we please quickly push a 3.0.1 update to JDO to include the
OSGi manifest fix that's in this patch? Long term, it would be nice to come up
with some tests to confirm proper OSGi manifests in all JDO artifacts. I feel
another issue coming on...and there it is: JDO-685.
> 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
> 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
