-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Migration Guide 3.6
date: 2023-11-29 --- :toc:
Note
|
We highly recommend the use of Items marked below with ⚙️ ✅ are automatically handled by |
After having been deprecated for a long while, the Jaeger and SmallRye OpenTracing extensions have been retired from the Quarkus Platform.
It is recommended to migrate your applications to OpenTelemetry and a tutorial is available.
The code of the extensions have been moved to the Quarkiverse and can be consumed from there from now on (relocations have been put in place to avoid breaking your builds). If you want these extensions to continue working in the future, it is recommended to be involved in their development.
These extensions are not in the Quarkus Platform BOM anymore and you need to define the version yourself in your build file, together with moving to the new groupId:
Component | New groupId | Current version | Repository | |
---|---|---|---|---|
Jaeger |
|
|
||
SmallRye OpenTracing |
|
|
https://github.com/quarkiverse/quarkus-smallrye-opentracing |
With version 3.6 the quarkus-bom version of the io.strimzi:strimzi-kafka-oauth
dependency is updated to 0.14.0
.
A known issue in this version causes native build failure with the error " Error: Substitution target for io.smallrye.reactive.kafka.graal.Target_com_jayway_jsonpath_internal_DefaultsImpl is not loaded.
.
The workaround until the upstream issue is resolved is to add the io.strimzi:kafka-oauth-common
dependency to the classpath of the Quarkus project.
Quarkus SmallRye JWT used to bring the quarkus-reactive-routes
extension prior to 3.6.
That is not the case anymore in 3.6.
So if you relied on Quarkus SmallRye JWT to bring the quarkus-reactive-routes
extension, add a dependency to quarkus-reactive-routes
in your build file.