On 30 May 2017 at 07:35, Chetan Mehrotra <[email protected]> wrote:
> On Tue, May 30, 2017 at 11:53 AM, Andrei Kalfas > <[email protected]> wrote: > > Looks to me that there is a dependency on oak functionality. > > Ian can confirm but I believe thats not required now (the component > does not get activated) and was only a temporary workaround. Oak > publishes the MetricRegistry instance in OSGi service registry and > then any component can look up that service and configure a reporter > for it > Correct. Older versions of Oak didn't publish the MetricsRegistry as a service so it had to be extracted from Oak forcibly. (;) Once older versions of Oak disappear, the dependency goes. I could have done it with the class name and no dependency, but that was more effort, and no one would have found the code to delete. Best Regards Ian > > Chetan Mehrotra >
