Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The specification says:
The OSGi framework resolver only considers Capabilities without an effective directive or effective:=resolve. Capabilities with other values for the effective directive can be considered by an external agent.
The effectiveness active is a convention commonly used for situations that do not need to be resolved by the OSGi framework but are relevant in using the resolver for assembling applications.
The feature resolver considers the capability as a strong requirement, whatever if it's effective or not.
I think it makes sense to consider this capability requirement for the build, but runtime could consider effective capability as optional.
It would be great to either update the features resolver that way or add a configuration in org.apache.karaf.features.cfg defining strong or optional requirement for effective cap.