discussed at the Sling Committer Round Table @ adaptTo() 2016 currently we have Slind launchpad with a quite monolithic configuration [1] one big list of all sling bundles), and we have a karaf feature repository [2] with nicely cut features for different aspects of sling, allowing the deployer to choose which sling features are wanted and which not, and which are the dependencies. oliver did today a talk on karaf/sling [3].
the launchpad should be split up in separates features/provisioning fragments to make it possible to easily build a "minimal launchpad" or "minimal launchpad + X" by selection only some but not all features. both launchpad features and karaf features should share a common source to avoid maintaining both in parallel. one could be generated from the other. stefan [1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/src/main/provisioning/sling.txt [2] https://svn.apache.org/repos/asf/sling/trunk/karaf/org.apache.sling.karaf-features/src/main/feature/feature.xml [3] https://adapt.to/2016/en/schedule/apache-sling-and-karaf-for-web-sites-and-applications.html
