[
https://issues.apache.org/jira/browse/JDO-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bouschen updated JDO-685:
---------------------------------
Fix Version/s: JDO 3 update 1
> Create tests for proper OSGi manifest entries
> ---------------------------------------------
>
> Key: JDO-685
> URL: https://issues.apache.org/jira/browse/JDO-685
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3, JDO 3 maintenance release 1, JDO 3 maintenance
> release 2
> Reporter: Matthew T. Adams
> Priority: Minor
> Labels: jdo-api, osgi
> Fix For: JDO 3 update 1
>
>
> After realizing that JDO 3.0's jdo-api-3.0.jar was released with incomplete
> OSGi manifest (see JDO-684), we should add tests that confirm that the JDO
> API jar can be successfully loaded into an OSGi container.
> I **think** it might be as easy as, for each target OSGi implementation
> (initially at least Felix & Equinox), we use its APIs (or OSGi standard ones,
> if they exist) to start & successfully activate the JDO API bundle.
> Note that these tests should be part of the api project, not the tck.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
