Michael Lipp created ARIES-1739:
-----------------------------------
Summary: Specifiying a version in Require-Capability prevents
registration
Key: ARIES-1739
URL: https://issues.apache.org/jira/browse/ARIES-1739
Project: Aries
Issue Type: Bug
Components: SPI Fly
Affects Versions: spifly-1.0.8
Reporter: Michael Lipp
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
