db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
Date Fri, 30 Sep 2011 20:28:46 GMT

     [ 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.3.patch

After our conf call, I found http://java.sun.com/developer/Books/javaprogramming/JAR/basics/manifest.html
that discusses "Package Versioning".  It's fairly old, and none of the headers specified therein
conflict with those specified in the OSGi r4 specification.  I have added these headers for
completeness with my best guess for their values, although I omitted the "Name:" header, as
it was causing bnd to throw errors.

WRT importing exported packages, section 3.6.6 of the OSGi r4 Core specification discusses
importing exported packages.  That discussion suggests that our bundle is not a candidate
for package substitution, as we mix implementation (JDOHelper) classes with API.

WRT Bundle-Version, section also says the "Bundle-Version header specifies the version
of this bundle."  For this release, then, it's "3.0.1".

WRT singleton bundles, section 3.6.2 says that it "Indicates that the bundle can only have
a single version resolved...The Framework must resolve at most one bundle when multiple versions
of a singleton bundle with the same symbolic name are installed."  I think this means that
we should go with the default value, false.  It does not address the authoritativeness of
a bundle.

Patch attached, relative to branches/3.0 (other patches were accidentally relative to branches/3.0/api);
this patch supercedes all other patches.  I would have deleted all other patches, but I don't
have the ability or couldn't figure out how to delete attached files.
> 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.3.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.
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


View raw message