db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Date Fri, 11 Nov 2011 18:21:52 GMT

    [ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148639#comment-13148639

Matthew T. Adams commented on JDO-694:

I'll defer to bnd's expertise as to what should be listed in the Import-Package header (bnd
is the tool that underlies maven-bundle-plugin).  For example, we depend on javax.security,
yet bnd does not add an import for that package, but it does add an import for javax.naming.
 Best Craig & I could figure is that bnd knows what should & shouldn't be listed in
Import-Package.  We're going with everything as optional because javax.naming & javax.rmi
are used only if JNDI is used and the XML APIs are used only if a jdoconfig.xml is parsed.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>                 Key: JDO-694
>                 URL: https://issues.apache.org/jira/browse/JDO-694
>             Project: JDO
>          Issue Type: Improvement
>          Components: api
>    Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>              Labels: jdo, osgi
>             Fix For: JDO 3 maintenance release 1
>         Attachments: JDO-694.patch
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other
packages for the purposes of use in an OSGi environment.

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