On Wednesday 08 April 2015 07:29:17 Carsten Ziegeler wrote: > Hi, Hi Carsten,
> as mentioned before I think we should move to the provisioning model and > replace the old xml based bundle list. > > The major features are implemented and the latest maven slingstart > plugin supports building and testing instances based on the provisioning > model. 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. https://svn.apache.org/repos/asf/sling/trunk/contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml > However, as we have several modules currently using the sling launchpad > plugin and the xml format, moving to the provisioning model is a larger > task. My suggestion is to do this incrementally, starting with the > launchpad and fixing things, implementing missing functionality when we > hit them. While this has the downside that we will have failing builds > for some time, I think it's the easier way and might lead to a more > collaborative work. > > If no one objects I'll start the work in the coming days. +1 Regards, O. > Regards > Carsten
