[ARIES-1739] Specifiying a version in Require-Capability prevents registration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: spifly-1.0.8
• Fix Version/s: spifly-1.2
• Component/s: SPI Fly
• Assignee: Raymond Augé
• Reporter: Michael Lipp
• Created: 23/Aug/17 10:18
• Updated: 13/Nov/18 17:18
• Resolved: 31/Oct/18 03:44

Description

The OSGi Compendium 6.0.0 provides an example for specifying a provider:

Require-Capability:
osgi.extender;
filter:="(&(osgi.extender=osgi.serviceloader.processor)
(version>=1.0)(!(version>=2.0)))"

This fails with spi-fly because spi-fly doesn't provide a version attribute when filtering the requirements, only the type (ProviderBundleTrackerCustomizer:390).

The example in the spi-fly documentation does not include the version in the filter. But it does also not warn you that adding it makes things fail. Having read the compendium specification first, you wouldn't expect that specifying the filter has this fatal effect.