Hi Jesse, You can use the install attribute on the features XML:
<feature name="foo" version="1.0" install="auto"> ... </feature> <feature name="bar" version="1.0" install="no"> ... </feature> only the feature with install="auto" will be installed when you deploy the kar file. Regards JB On 07/11/2018 00:09, Jesse White wrote: > All; > > We're interested in leveraging .kar files to help package plugins and > extend our platform but we've run into a snag. > > If a .kar file contains many features and we want to let the user > control which feature(s) to install, is there a way to have these > features installed automatically on a clean start? > > So far we've tried setting 'Karaf-Feature-Start=false' in the .kar files > manifest to prevent *all* of the features from being automatically > installed. User's can then configure and install the features they need, > but there doesn't appear to be a built-in way to make these persist > after a clean start. > > Normally we would use the 'featuresBoot' property for this, but in the > case of a clean start it appears that the .kar and the feature > repository defined in the .kar are not yet available when these > statements are processed. > > I'm wondering if there's a way around this that we're not aware of. If > there isn't, is there any interest in solving this use case directly in > Karaf? > > There are some more details on our use case and what we've tried here: > https://issues.opennms.org/browse/HZN-1436 > > Thanks, > Jesse > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
