On Tue, 2018-02-13 at 11:51 +0100, Oliver Lietz wrote: > > 1. Move the service to oak-core. > > 2. Require oak-store-composite for deployments > > > > If we go with 1, we have simpler deployments ( one less bundle ). > > If we > > go with 2, we split the logic from the oak-store-composite bundle > > and > > add more stuff on top of oak-core. > > 1 means simpler deployment and more stuff in oak-core, but the > MountInfoProvider is required for composite and non-composite stores. > Having it in (experimental) module oak-store-composite feels strange.
Why do you consider oak-store-composite experimental? It's not documented very well unfortunately, but it's as well-tested as any other component in Oak from my point of view. Robert
