Hi Andreas, Sling Feature Model "Launcher" is built primarily for building immutable instances from scratch. The feature model definition itself doesn't mandate any runtime behavior in particular but is supposed to describe a target state, so it is up to any implementation to take care of establishing this target state. If you want to make full use of the feature model and the existing tooling (checking for coherence etc.) the target state as feature model would be kept by what ever keeps track of the system state. The direction we took with feature launcher is to always build it from scratch and decouple the application and content part (libs&apps + osgi state vs all other content parts) with the help of composite node store in Oak which allows to build throw away instances to be used on persisting mutable node storage.
documentation of the feature model is here: https://github.com/apache/sling-org-apache-sling-feature/blob/master/readme.md But I agree the launcher section - refers to the readme of the launcher which mostly points back to the generic documentation - so it could get some love. Some indicator about use can be found in the parseArgs section: https://github.com/apache/sling-org-apache-sling-feature-launcher/blob/org.apache.sling.feature.launcher-1.0.0/src/main/java/org/apache/sling/feature/launcher/impl/Main.java#L83-L93 HTH Dominik On Fri, Apr 5, 2019 at 5:33 PM Andreas Schaefer <schaef...@me.com.invalid> wrote: > Hi > > I am looking into the Sling Feature Model to deploy content packages in a > custom sling build similar to the sling provisioning. > > Is there an example or documentation on: > - how to deploy a feature module into a running sling instance? > - how to create a custom sling build with feature models? > > Cheers - Andreas Schaefer
