TCK does not work with MP Metrics 5.0

MP Metrics 5.0 is bringing in breaking changes which require changes in the Fault Tolerance TCK.

The ones that I think affect the Fault Tolerance TCK are:

• @RegistryType is removed, replaced with @RegistryScope
  • @RegistryScope is not a qualifier which means we can’t look it up with CDI.current().select()
  • The only way to get hold of the MetricsRegistry for the base scope is to inject it into a bean with the @RegistryScope annotation
• Some methods have been removed from Snapshot, particularly getValues() and getMedian()
  • The median can likely be obtained from the new getPercentileValues() array
  • There’s no replacement for getValues() - several of our tests used this to assert that the correct data had been added to the histogram
• Gauge<T> has been changed to Gauge<T extends Number> which breaks binary compatibility because it changes the signatures of methods which return T

I don’t think there are any changes needed to the spec or API to accomodate MP Metrics 5.0, just to the TCK.

[Azquelt]

But I think we’re saying the same thing, it would be better if they made it a qualifier, made scope non-binding and used getQualifiers() to find the annotation. Firstly because it is acting as a qualifier so having it be one makes sense and secondly it would make it possible to look up using CDI.current().select().

[Azquelt]

TCK update to add compatibility with Metrics 5.0 released as 4.0.2