You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jacek Laskowski (JIRA)" <ji...@apache.org> on 2011/06/06 22:10:58 UTC
[jira] [Created] (ARIES-670) blueprint.api bundle exports
org.osgi.service.blueprint package at version 0.0.0
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-670) blueprint.api bundle exports
org.osgi.service.blueprint package at version 0.0.0
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063568#comment-13063568 ]
Alasdair Nottingham commented on ARIES-670:
-------------------------------------------
The relevant section of the blueprint specification is 121.13.5 Type Compatibility. It states that:
To mitigate type incompatibility problems, a Blueprint extender must export the org.osgi.service.blueprint package. In the uses: directive, it should list any packages of classes that can be shared between the Blueprint extender and the Blueprint bundle. Blueprint bundles should import this package.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-670) blueprint.api bundle exports
org.osgi.service.blueprint package at version 0.0.0
Posted by "Matt Bishop (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063541#comment-13063541 ]
Matt Bishop commented on ARIES-670:
-----------------------------------
I have searched the R4.2 compendium and I can't find anything related to exporting org.osgi.service.blueprint as a package. I get why, it makes sense, but I don't see the "strong" encouragement to do so.
The reason is that I filed a bug in Gemini to export this package (https://bugs.eclipse.org/bugs/show_bug.cgi?id=351755) but I couldn't cite the chapter/verse to back it up.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-670) blueprint.api bundle exports
org.osgi.service.blueprint package at version 0.0.0
Posted by "Holly Cummins (JIRA)" <ji...@apache.org>.
[ 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