- yes, we want to switch - and soon, so it can be part of sling 12 - what the feature model tooling is currently missing is building a combined jar file or WAR file - for this it's planned to start with a "bridging solution", that means generating a provisioning out of the feature models and build the combined jar and WAR files from it - it's still good to provide a combined jar file for non-docker use cases, it's a counterpart to what sling boot provides as well - for WAR file there still might be rare use cases as well
- granularity of the features defined: start with putting the whole sling starter in a feature model, and later think about breaking it down to smaller features - note: feature model does not allow to define dependencies to other features - this does not allow to map the current list of karaf features directly to sling features, as they are very finegrained and heavily rely on features depending on features - it would also be nice to habe an maven archetype which sets up a feature model-based sling application project stefan
