MicroProfile OpenTracing TCK Dependencies

32 views
Skip to first unread message

John D. Ament

unread,
Jan 11, 2018, 9:54:41 PM1/11/18
to Eclipse MicroProfile
Hi,

I want to follow up on a discussion we were having on gitter to make others aware.  While trying to test an implementation of the MP OpenTracing spec, I found that the TCK requires a number of features not currently required by a MP spec.  I'm wondering how should we deal with them?

- The ability to read a TestTracer from JSON, on the client side.
- A direct dependency on Jackson on the server side (I'm assuming to generate the above JSON)

There's also a hard dependency on a specific implementation (RestEasy client) which makes some assumptions about how the spec works (e.g. JAX-RS client automatically has features registered, but it relies on an implementation specific behavior).

Kevin Sutter

unread,
Jan 15, 2018, 1:55:42 PM1/15/18
to Eclipse MicroProfile
 Hi John,
The dependencies for the RestEasy client and the Jackson library for the TCK were documented and approved via this CQ:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15198

Since they were classified as build and test dependencies, they can be lumped into a single CQ instead of individual CQs (which are needed if the shipped "product" requires them).  Since the TCK is required for implementations of the API and not the API itself, we have been treating the TCK dependencies as build and test dependencies.

As far as the assumptions with regard to the RestEasy implementation, we'll need some input from Steve on that.

--  Kevin
Reply all
Reply to author
Forward
0 new messages