davsclaus opened a new pull request, #29048:
URL: https://github.com/apache/camel/pull/29048

   ## Summary
   
   `camel-observation` imports `opentelemetry-bom` and 
`opentelemetry-bom-alpha` (as `camel-opentelemetry2` already does), so all 
`io.opentelemetry` jars on its test classpath use `${opentelemetry-version}`.
   
   ## Why
   
   `micrometer-tracing-integration-test` 1.7.2 brings in 
`opentelemetry-sdk-common`, `opentelemetry-sdk-trace`, 
`opentelemetry-extension-trace-propagators` and others at **1.62.0**. Maven 
picks these over the `${opentelemetry-version}` jars that 
`opentelemetry-sdk-testing` brings in, because they are closer in the 
dependency tree. That only worked by luck: in OpenTelemetry 1.67.0, 
`ConfigUtil` moved from `opentelemetry-api` to `opentelemetry-common`. With the 
bump in #28992, every test in the module fails with `NoClassDefFoundError: 
io/opentelemetry/api/internal/ConfigUtil` (diagnosis in 
https://github.com/apache/camel/pull/28992#issuecomment-6590056073).
   
   `opentelemetry-exporter-zipkin` stays at 1.62.0: OpenTelemetry no longer 
publishes it after 1.64.0, so it is not in the BOM, and it does not use the 
class that moved.
   
   ## Testing
   
   In `components/camel-observation`:
   - `mvn dependency:tree -Dincludes=io.opentelemetry` with 
`-Dopentelemetry-version=1.67.0`: every OpenTelemetry jar resolves to 1.67.0, 
except the zipkin exporter.
   - `mvn test` with `-Dopentelemetry-version=1.67.0 
-Dopentelemetry-alpha-version=1.67.0-alpha`: 17 tests pass (they all fail 
without this change).
   - `mvn test` with the current 1.66.0: 17 tests pass.
   
   Once this is merged, #28992 can be rebased (`@dependabot rebase`).
   
   _Claude Code on behalf of davsclaus_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to