On Wednesday 09 November 2016 10:23:35 Carsten Ziegeler wrote: > Bertrand Delacretaz wrote > > > On Wed, Nov 9, 2016 at 10:11 AM, Carsten Ziegeler <[email protected]> wrote: > >> ...When the RepositoryInitializer arrives later it is completely > >> ignored... > > > > Do you know why it arrives too late? That could be a wrong start level > > of its bundle, or unwanted dependencies that cause it to start too > > late. > > I don't want to depend on fragile start level ordering.
+1 > However, right > now repoinit has the default start level (20) and Oak has 15. Clearly > that setup is not going to fly at all. Surprisingly it did so far in > most cases, only Jenkins is not happy with it. aahh, may be the cause for trouble with restricting rights for everyone (SLING-6130). O. > >> ...easiest fix would be to make a > >> RepositoryInitializer required, but then this would mean only one of > >> them is required.... > > > > That's the typical "we have 0..N plugins, how to wait on them > > problem". I don't think we've found a better way so far that start > > those plugins at a low enough start level. Or configure how many of > > those services you are expected but that's painful. > > That's how you usually solve it in DS as you can specify a minimum > number of required services. > We could at least require 1 repository initializer > > Carsten
