Re: Backwards incompatible opentelemetry-semconv in 4.0.5

Hi, I just wanted to give a notice that after some discussion, Quarkus team upgraded to opentelemetry-semconv 1.26.0-alpha in their 3.8.6 release, and so I was able to upgrade to CXF 4.0.5 in Quarkus CXF

Re: Backwards incompatible opentelemetry-semconv in 4.0.5

Thanks for the prompt reply, Andriy. After having a closer look at the changes in opentelemetry-semconv post 1.24.0-alpha, I found that the removed classes were introduced back in this commit

Backwards incompatible opentelemetry-semconv in 4.0.5

Hi, as you may know I am the maintainer of Quarkus CXF . When trying to upgrade CXF from 4.0.4 to 4.0.5 in our 3.8 LTS branch, I found out that it won't work because of missing class io.opentelemetry.semconv.HttpAttributes. It is caused by this u

Re: [VOTE] Release CXF 4.0.4

+1 (non-binding) Thanks for cutting the release, Freeman! I have tested Quarkus CXF against CXF 4.0.4 staging repo and found no issues: https://github.com/quarkiverse/quarkus-cxf/pull/1274 -- Peter On 05/03/2024 22:57, Freeman Fang wrote: It’s been a while since the last release and many is

Re: Plans for release 4.0.4?

Thanks, great to hear that, Andriy. It would be great if we could get https://github.com/apache/cxf/pull/1660 merged in some form before the release. The main motivation is to be able to run CXF on FIPS-enabled systems. If the customized algo suite, that the PR proposes, is questionable, I'd b

Plans for release 4.0.4?

Hi, we are preparing Quarkus CXF to release it for Quarkus 3.8 which is going to be a LTS (Long Term Support) release. I wonder whether we could count on getting CXF 4.0.4 by February 21st to be able to use it in that release? Thanks, -- Peter