Hi, On Wed, Nov 9, 2016 at 11:50 AM, Carsten Ziegeler <[email protected]> wrote: > ...We only have a single RepositoryInitializer service registered which is > configured to read the repoinit stuff from the embedded provisioning > model....
Right but Sling users can register more RepositoryInitializer at will, and those should be executed in the same phase, before making the SlingRepository service available. > ...We should provide a guarantee that at least the repoinit part contained > in the provisioning model is applied before the repository service is > made available. This needs to be configurable again for the same reason > as above (not using Launchpad or not having repoinit)... Agreed and this is the "require at least one RepositoryInitializer" option that you suggested IIUC. My suggestion is to instead implement a configurable "require N RepositoryInitializer services" option, which solves the problem that you mention as well as the one of users registering additional RepositoryInitializer services. -Bertrand
