FYI, I have to fixup the current PR because I goofed up, but I'm doing that now.
On Tue, May 15, 2018 at 5:00 PM, Romain Manni-Bucau <[email protected]> wrote: > Hi Raymond > > Does it mean we can drop the providerlocator now? > Not with this change. I believe you are referring to the Service Loader Mediator [1] (like Aries SpiFly [2]), which I could do as a second PR if that is really wanted. > > +1 anyhow for the pr > Great! thx [1] https://osgi.org/specification/osgi.cmpn/7.0.0/service.loader.html [2] http://aries.apache.org/modules/spi-fly.html > > > Le mar. 15 mai 2018 21:52, Raymond Auge <[email protected]> a > écrit : > >> Hello All, >> >> As some of you know several of the OSGi RIs consume the specification >> bundles produced by the Apache Geronimo project. >> >> In the last couple of OSGi releases we've been applying the requirement >> for Portable Java Contracts as part of new and updated specs. Now as the >> specs of OSGi Release 7 have finalized we're in need to close out the RIs. >> >> To that end I'd like to request the application of the Portable Java >> Contracts to the Geronimo spec bundles. >> >> I've created an issue [1] and sent a PR [2] which makes the necessary >> changes. >> >> Would someone be so kind as to review this? >> >> Next, if acceptable, would someone call a release? I'm not sure of the >> specs can be released all at once, but that would be the best case scenario. >> >> Sincerely, >> - Ray >> >> [1] https://issues.apache.org/jira/browse/GERONIMO-6606 >> [2] https://github.com/apache/geronimo-specs/pull/9 >> >> -- >> *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)
