[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.2.patch
After our conf call discussion, I ran bnd against our currently published 3.0
jar (http://repo1.maven.org/maven2/javax/jdo/jdo-api/3.0/jdo-api-3.0.jar) and
it's noticing that I missed some other import package statements:
C:\temp\jdo-bnd>java -jar biz.aQute.bnd.jar print -verify jdo-api-3.0.jar
One error
1 : Unresolved references to [javax.naming, javax.rmi, javax.xml.parsers,
org.w3c.dom, org.xml.sax] by class(es) on the
Bundle-Classpath[Jar:jdo-api-3.0.jar]: [javax/jdo/JDOHelper$12.class, javax
/jdo/spi/JDOImplHelper.class, javax/jdo/JDOHelper.class]
I'm going to add these to the manifest as well. New patch attached with those
as well. Please review. If ok, I'll commit then begin release process for JDO
3.0.1.
> 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.2.patch, 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
