On Friday 30 September 2016 14:00:23 Carsten Ziegeler wrote: > Stefan Seifert wrote > > > 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. > Atm the provisioning model has a slightly larger function set as karaf > features. We have support for framework properties and things like the > repo init stuff.
I didn't find the statement in the OSGi spec (R6 core) you mentioned at adaptTo() which says framework properties can be set at runtime. I'm quite sure I looked at Felix source and docs (e.g. [1]) when it was a topic last year and didn't find anything there also. Can you point me to any significant source? (just to make sure it makes sense to have framework properties in features at all) [1] http://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html Thanks, O. > The text based format is also easier to diff than XML. > > The OSGi alliance defines a YAML format for configurations which I would > like to directly support in the provisioning model (or whatever we use > as the source). > > And we have tooling like crankstart that can take a provisioning model > directly and launch the instance. > > This all leads me to the suggestion that we keep the provisioning model > and generate the karaf features xml out of this. As the provisioning > model supports features already we can directly create the features in > the launchpad provisioning model as they are currently defined for karaf. > > > > Regards > > Carsten
