Hi I like the Sling subsystem generation very much. So we should maybe add some brain juice here.
Yet: Am 27.09.2014 um 13:23 schrieb Oliver Lietz <[email protected]>: > On Tuesday 23 September 2014 21:18:14 David Bosschaert wrote: >> >> So I guess my attempt is more or less a failed experiment, but I'm >> wondering if other people might have a better idea on how to create a >> subsystem archive for Sling? > > I hope to have some time next week to look into it and the common model > Carsten and Bertrand are working on. For Karaf we now have several features > and you only need to install what your application needs. Do you plan > something similar with subsystems or will there be only one subsystem for > Sling? That *is* an intriguing idea, indeed: We should not generate a single subsystem but probably multiple ones. One subsystem that comes to mind quickly is the repository: You can package all the modular dependencies of the repository into a subsystem without polluting the class space of the rest of Sling (or the system) in that only the JCR and Jackrabbit APIs are exposed from the subsystem. Regards Felix
