I apologize if this is a stupid question. I've been trying to understand how to leverage capabilities and requirements in a way to allow defining the provisioning of a system by specifying requirements in a feature.
I've read through the posts on the mailing list about it, the docs and the karaf features.xml but haven't found the information I am looking for. I also tried some experiments with a bundle providing a capability and a feature requiring it but it didn't seem to work. I am wondering if I am just over thinking or over complicating it in my head. Here are the questions: 1. When a feature specifies a requirement, what is the "scope" of resolution used by the feature resolver? Meaning, does it only pick from features specified within that feature with dependency=true specified? Or from any feature defined in the features.xml and any feature repository defined that provides a satisfying capability? 2. Can you specify a requirement in a feature for a requirement provided by a bundle? 3. If a bundle or feature provides a capability, but you don't specify you require it. Does it always get considered for installation if it's in a feature that doesn't have dependency=true? Part of this is because I still can't understand when to use dependency=true for a feature. I am primarily talking about custom capabilities and requirements I make up myself for a system to pull things in. Not sure if the above questions fully make sense, having a hard time articulating exactly what I am trying to figure out. Thanks for any help! Ryan
