[
https://issues.apache.org/jira/browse/ARIES-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holly Cummins resolved ARIES-670.
---------------------------------
Resolution: Fixed
Assignee: Holly Cummins
As part of ARIES-754, an export of the org.osgi.service.blueprint package was
added to the blueprint-core bundle, with version 1.0.0. This means we do have
the correct export, which is good, but have two exports, which is bad. Core
seems like the appropriate bundle for the export, since it's the Extender which
should have the export.
It looks like the export on the api bundle is actually a side effect of the bnd
pattern used to export the org.osgi.service.blueprint.container and .reflect
packages, rather than a deliberate export (and . doesn't seem to be escaped
properly).
> blueprint.api bundle exports org.osgi.service.blueprint package at version
> 0.0.0
> --------------------------------------------------------------------------------
>
> Key: ARIES-670
> URL: https://issues.apache.org/jira/browse/ARIES-670
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: 0.4
> Reporter: Jacek Laskowski
> Assignee: Holly Cummins
>
> As per discussion in the dev mailing list:
> "The core bundle has this import package:
> org.osgi.service.blueprint;version="[1.0.0,2.0.0)". The api bundle exports
> the package but at version 0.0.0 (which is the bug). It works for the 'uber'
> bundle because everything is in the one bundle, and there is no import or
> export for this package. Please would you open a JIRA bug for this. Thank
> you."
--
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
