Hi, Am 08.04.15 um 13:07 schrieb Oliver Lietz: > > I hadn't time to look deeper into the new provisioning model (still on my > TODO) and adapt it for Karaf. > > Can it represent features or subsystems and their dependencies and > capabilities (as we discussed with David Bosschaert at last year's adaptTo() > conf) already? I spent quite some time to shape the features we now have in > Karaf Launchpad and don't want to loose that information. > right now, the provisioning model is a little bit more powerful than the XML format. We could easily get to a solution where each model is translated into a subsystem. It would then need additional tooling to create the requirements and capabilities for such a system. This can either be done by analyzing the contained bundles and aggregating that information (at least partially), but we could also come up with some way of describing them in the model. This is definitely something we should do. But I think the first step would be to move to the provisioning model and build the whole thing up from there.
Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
