[OAK-7380] Add missing OSGi capabilities

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 1.8.2
• Assignee: Unassigned
• Reporter: Oliver Lietz
• Created: 28/Mar/18 11:14
• Updated: 16/Mar/22 08:58
• Resolved: 16/Mar/22 08:58

Description

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):

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

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.

Issue Links

• is related to: SLING-7546 Take requirements for services into account