Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
When possible, it's a good practice to have features linked together via capability/requirement. For instance, instead of defining inner feature http , it's better to use the http requirement. It allows users to choice between felix http or pax web for instance.
The problem is the verify goal which expects at least a feature providing the capability "installed" to verify the requirement.
It would be great to have a configuration to define a "default requirement provider" somehow for a feature.