Worse case i can do it but not before a week.

Idea is to have each event chains handling a single case.

Versions are 2 cases so should be two chains.

As mentionned in the review it means moving the toggle to the extension probably and drop instanceof from the observer to add typed observes instead of using the base class in the observer.

The thing to take care is to keep our common structure since this code is usable in standalone anf osgi but nothung crazy.

I put a few others notes in the review, one about the doc / backward compat which had been broken - i dont know if ok or not to be honest.

If unclear im happy to fix it all next friday.

Le ven. 3 mai 2019 à 20:56, Jean-Louis MONTEIRO <> a écrit :
Can you elaborate?
Not sure I understand. But happy to work on it.

Le ven. 3 mai 2019 à 18:17, Romain Manni-Bucau <> a écrit :

Can do in a week

Can we ensure we have 2 converters before releasing? We should have a single path per converter IMO - the extension vetoing other IIRC.

Le ven. 3 mai 2019 à 16:19, Jean-Louis MONTEIRO <> a écrit :
Hi team,

Can someone mark OpenTracing_1.0.2 has being released in JIRA.
I'd like to merge Jon's PR and create a release with the Zipkin fix.

OpenTracing_1.0.3 already exists. I would need someone to mark it as released when vote passes, and someone to create a OpenTracing_1.0.4 in case we have other bug fixes. And maybe a OpenTracing_1.1.0 for the next iteration?