[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13122408#comment-13122408
]
Craig L Russell commented on JDO-684:
-
Looks good. Just one minor question. The patch updates api/API3.MF which looks
fine.
But it also updates API3.MF. Is this file obsolete? Most of the changes do not
appear in this file...
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira