You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Oliver Lietz (Jira)" <ji...@apache.org> on 2022/03/16 08:59:01 UTC

[jira] [Resolved] (OAK-7380) Add missing OSGi capabilities

     [ https://issues.apache.org/jira/browse/OAK-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Lietz resolved OAK-7380.
-------------------------------
    Resolution: Abandoned

> Add missing OSGi capabilities
> -----------------------------
>
>                 Key: OAK-7380
>                 URL: https://issues.apache.org/jira/browse/OAK-7380
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>    Affects Versions: 1.8.2
>            Reporter: Oliver Lietz
>            Priority: Major
>
> For resolving bundles (Karaf and Sling/OSGi features) at compile-time it's essential to have the proper meta data in place. The following capabilities are missing from Oak (to get up Sling, probably more):
> {noformat}
> osgi.service;objectClass=org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore
> osgi.service;objectClass=org.apache.jackrabbit.oak.spi.blob.BlobStore
> osgi.service;objectClass=org.apache.jackrabbit.oak.api.jmx.CacheStatsMBean
> osgi.service;objectClass=org.apache.jackrabbit.oak.api.jmx.QueryEngineSettingsMBean
> osgi.service;objectClass=org.apache.jackrabbit.oak.spi.mount.MountInfoProvider
> osgi.service;objectClass=org.apache.jackrabbit.oak.spi.security.SecurityProvider
> osgi.service;objectClass=org.apache.jackrabbit.oak.spi.state.NodeStore
> osgi.service;objectClass=org.apache.jackrabbit.oak.spi.state.NodeStoreProvider
> osgi.service;objectClass=org.apache.jackrabbit.oak.stats.StatisticsProvider
> {noformat}
> Usually bnd adds meta data for capabilities to {{MANIFEST.MF}} when building bundles but does not take services into account when using e.g. {{BundleContext.registerService(...)}}.
> See SLING-7546.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)