Ok this thread gets a little longer than I expected. Let me recap: today there is zero guarantee that the RepositoryInitializer is used before the Repository is made available.
We only have a single RepositoryInitializer service registered which is configured to read the repoinit stuff from the embedded provisioning model. This limits the usage more or less to launchpad atm. We all agree that we might need a more dynamic mechanism, especially if people are not running Sling's launchpad, like Karaf. 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) There might be future enhancements in one or the order direction, but we don't have a clear picture yet. Does anyone disagree with this? Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
