James Netherton
James Netherton
Milo was removed in Camel 4.x.
> pass them to surefire/failsafe via properties That's a pain for platform integration though. Because you have to do the same change(s) there. What I was thinking, is that we...
This was fixed in 3.0.0-M2 by https://github.com/apache/camel-quarkus/pull/4739.
This happens because Quarkus Google Cloud Services is forcing an older version of bigquery-java to what we expect for CQ. It should get resolved once that projects integrates a new...
This has been fixed now that Quarkus Google Cloud Services and Camel are aligned better.
Have you tried with the latest Quarkus 3.7.3 release? I see some open issues in Quarkus documenting a similar problem. https://github.com/quarkusio/quarkus/issues/25102 https://github.com/quarkusio/quarkus/issues/35686
> everything that ends in Final is the most stable according to the documentation Not quite. The `.Final` suffix has actually been removed in recent Quarkus releases. However Quarkus &...
It depends what your requirements are. Take a read through this: https://quarkus.io/blog/lts-releases/ Quarkus 3.8.0 will be released soon, which is the next LTS release.
> it's just a warning Yeah, but something is likely going wrong somewhere. Have you checked that the all of the expected traces / spans are delivered to the OpenTelemetry...
> What are you suggesting ? That whatever is going wrong to cause the `WARN` message, may affect your application tracing. Hence, why checking the results would be a good...