[
https://issues.apache.org/jira/browse/FELIX-6521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526491#comment-17526491
]
Tom Watson commented on FELIX-6521:
-----------------------------------
I'm suggesting we follow the most recent guidelines that OSGi published on the
topic to [Embed or Not To Embed Your API
Packages|https://blog.osgi.org/2020/01/to-embed-or-not-to-embed-your-api.html]
{quote}Going forward, to support all environments for your bundles, you should
consider not embedding API packages that are defined by OSGi specifications.
The better approach is to declare them as dependencies using Import-Package
manifest headers{quote}
[~cziegeler] you may recall having a hand at writing that blog post up.
Even if the OSGi API published JARs also imported their exports it still can
cause problems for things like OSGi connect when multiple JARs are on the
classpath or modulepath.
> Stop exporting org.osgi.service.component packages
> --------------------------------------------------
>
> Key: FELIX-6521
> URL: https://issues.apache.org/jira/browse/FELIX-6521
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Tom Watson
> Priority: Major
>
> I would like to stop exporting the org.osgi.service.component packages from
> the SCR bundle and instead only import them. This is to make the
> implementation more predictable when installed along side the OSGi
> specification API bundle with GAV org.osgi:org.osgi.service.component:1.5.0
> which only exports and does not import this package. This will reduce the
> confusion and possible issues with multiple exporters of that package.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
