Provide a way to select which features are to be installed when dropping a descriptor to the deploy folder.

Details

Description

Currently when dropping a feature in the deploy folder it automatically starts all features (including transient).
However, there are cases that the use doesn't want to install all of them. We need to provide a way to select which of the features are to be installed.

Activity

Lets also consider lining up karaf feature support more with what's in the osgi subsystem spec. There, a subsystem (including a feature) is a jar with some manifest-like files indicating its contents (and isolation, etc etc). In particular there isn't an idea of a "feature repository" containing several features. I think you can represent a "feature repository" with an obr xml repository document, but I haven't tried.

From this point of view, the problem is that we should be using features rather than feature repositories. Then its pretty clear what to do if you deploy a single feature.

David Jencks
added a comment - 12/Oct/11 23:25 Lets also consider lining up karaf feature support more with what's in the osgi subsystem spec. There, a subsystem (including a feature) is a jar with some manifest-like files indicating its contents (and isolation, etc etc). In particular there isn't an idea of a "feature repository" containing several features. I think you can represent a "feature repository" with an obr xml repository document, but I haven't tried.
From this point of view, the problem is that we should be using features rather than feature repositories. Then its pretty clear what to do if you deploy a single feature.