[ https://issues.apache.org/jira/browse/JDO-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-685: --------------------------------- Affects Version/s: (was: JDO 3 maintenance release 2) (was: JDO 3 maintenance release 1) JDO 3 > 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 > Reporter: Matthew T. Adams > Priority: Minor > Labels: jdo-api, osgi > > 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. 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