Wouldn't it make sense in these "we have 0..N *mandatory* plugins, how to wait on them problem" situations to explicitly configure all required dependencies on the consuming service, e.g. by PID. This would make it robust and allow for correct ordering. Of course the additional configuration constitutes an overhead, but I think if the dependencies are mandatory, this information needs to live somewhere.
Regards Julian On Wed, Nov 9, 2016 at 10:15 AM, Bertrand Delacretaz <[email protected]> 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. > >> ...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. > > -Bertrand
