Hi,
MP 6.1:
• Depends on Config 3.1 (the included implementation already supports 3.1)
• Requires OpenTelemetry 1.1 (open task)
• Requires Metrics 5.1 (open task)
We're open to contributions in these areas. Although this should ideally be a
simple minor version update, experience shows it may take additional effort to
ensure the related TCKs pass successfully.
For example, simply bumping OpenTelemetry to 1.1 (Smallrye 2.7.0) results in:
[ERROR] JaxRsClientAsyncTest.testIntegrationWithJaxRsClient » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR]
JaxRsClientAsyncTest>Arquillian.run:137->testIntegrationWithJaxRsClientAsync:103->readSpans:157
» ConditionTimeout Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [3] but found [0] within 10 seconds.
[ERROR]
JaxRsClientAsyncTest>Arquillian.run:137->testIntegrationWithJaxRsClientError:109->readErrorSpans:114
» ConditionTimeout Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [3] but found [0] within 10 seconds.
[ERROR] MpRestClientAsyncTest.testIntegrationWithMpRestClient »
NoClassDefFound io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR]
MpRestClientAsyncTest>Arquillian.run:137->testIntegrationWithMpRestClientAsync:108->readSpans:113
» ConditionTimeout Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [3] but found [0] within 10 seconds.
[ERROR]
MpRestClientAsyncTest>Arquillian.run:137->testIntegrationWithMpRestClientAsyncError:102->readSpansError:148
» ConditionTimeout Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [3] but found [0] within 10 seconds.
[ERROR] OpenTelemetryBeanTest>Arquillian.run:137->testOpenTelemetryBean:55
expected object to not be null
[ERROR] OpenTelemetryBeanTest>Arquillian.run:137->testSpanAndTracer:60
NullPointer
[ERROR] BaggageTest.baggage » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] PropagatorSpiTest.testSPIPropagator » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] RestSpanTest.span » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] RestSpanTest>Arquillian.run:137->spanName:148 » ConditionTimeout
Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [1] but found [0] within 10 seconds.
[ERROR] RestSpanTest>Arquillian.run:137->spanNameWithoutQueryString:162 »
ConditionTimeout Assertion condition defined as a
org.eclipse.microprofile.telemetry.tracing.tck.exporter.InMemorySpanExporter
expected [1] but found [0] within 10 seconds.
[ERROR] CustomizerSpiTest.testCustomizer » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] ExporterSpiTest.testExporter » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] ResourceSpiTest.testResource » NoClassDefFound
io/opentelemetry/semconv/trace/attributes/SemanticAttributes
[ERROR] SamplerSpiTest>Arquillian.run:137->testSampler:60 NullPointer
On the Open Telemetry 1.1 TCK, i.e. some work needs to be done in order to fix
that.
MP 7:
Still requires substantial work, including updates to the CXF REST client and
other specifications. There have been some discussions on the CXF side, but
they won’t be making that update for 4.1.x (EE10).
As a result, MP 7 can only be done if we either fork and update the CXF client
ourselves, or wait for them to implement with EE11.
Please keep in mind that all work on these specifications is done voluntarily.
No one is being paid for their contributions—everything is developed in
peoples' spare time.
This means there's no fixed ETA for any specific feature or version; progress
happens as people need certain capabilities and step up to implement them.
Gruß
Richard
> Am 22.04.2025 um 18:14 schrieb COURTAULT Francois
> <francois.courta...@thalesgroup.com.INVALID>:
>
> THALES GROUP LIMITED DISTRIBUTION to email recipients
>
> Hello everyone,
>
> When could we expect to get a TomEE version compliant with µProfile 6.1 or 7 ?
>
> Best Regards.
>
>
>
>
