jaedonP commented on code in PR #7272:
URL: https://github.com/apache/incubator-kie/pull/7272#discussion_r4528205226


##########
kie-quarkus-build-parent/pom.xml:
##########
@@ -39,15 +39,11 @@
   </description>
 
   <properties>
-    <!--
-      [CVE-2026-45292] opentelemetry-api 1.57.0 pulled in via 
smallrye-reactive-messaging-otel.
-      Pin to 1.62.0 before quarkus-bom import so this value takes precedence.
-      Should be removed in future Quarkus upgrades that include OpenTelemetry 
>= 1.62.0
-    -->
-    <version.io.opentelemetry.api>1.62.0</version.io.opentelemetry.api>
-    
<version.io.opentelemetry.instrumentation>2.28.1-alpha</version.io.opentelemetry.instrumentation>
-    <version.io.quarkus>3.33.4</version.io.quarkus>
-    <version.io.quarkus.camel>3.33.2</version.io.quarkus.camel>
+    
<version.com.aayushatharva.brotli4j>1.24.0</version.com.aayushatharva.brotli4j>
+    <version.io.opentelemetry.api>1.67.0</version.io.opentelemetry.api>
+    
<version.io.opentelemetry.instrumentation>2.33.0-alpha</version.io.opentelemetry.instrumentation>

Review Comment:
   Hi @yesamer. The earlier OpenTelemetry bump (#7244) moved only 
opentelemetry-api to 1.67.0 and left the instrumentation BOM at 2.28.1-alpha, 
which imports the 1.62.0 OpenTelemetry BOM. That is the same kind of version 
mismatch that caused the native-image failures fixed in #7112, and it's 
probably why #7244 was reverted (#7246 doesn't state a reason). This PR moves 
opentelemetry-api (1.67.0) and the instrumentation BOM (2.33.0-alpha, which 
imports 1.67.0) together, and the resolved tree is consistent. I am trying to 
run the native ITs locally



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to