Re: Backwards incompatible opentelemetry-semconv in 4.0.5

Hi Peter, Thanks a lot for the update! Best Regards, Andriy Redko PP> Hi, PP> 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 abl

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 a lot Peter, that's great news, looking forward towards the (possible) release!   Best Regards,     Andriy Redko  > 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 introdu

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

Re: Backwards incompatible opentelemetry-semconv in 4.0.5

Hi Peter, That is unexpected, sorry about that. The minor updates are generally considered safe but dependency on *-alpha artifacts is definitely in conflict here (both for CXF or/and Quarkus). May be the best option for CXF and Quarkus would be to wait for semconv to become stable and only tha