Ok, that's all I needed to hear. I'll file a bug report and try to make a test case.
Thanks, - Ray On Thu, May 17, 2018 at 1:24 AM, David Bosschaert < [email protected]> wrote: > Hi Ray, > > Sounds like a bug to me. It shouldn't be restricted by start ordering. > Would it be possible to file a bug? > > Best regards, > > David > > On 16 May 2018 at 18:38, Raymond Auge <[email protected]> wrote: > >> Is the Service Loader Mediator known to be constrained by start ordering? >> >> In other words, I'm finding that spifly is having issues when not >> "started" before other bundles that specify the requirements and or >> capabilities on osgi.serviceloader. >> >> -- >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> (@rotty3000) >> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> >> (@OSGiAlliance) >> > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
