-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.2.0 seems to break compatibility with Spring Boot 3.1.5 #456
Comments
This is OpenTelemetry breaking you not Micrometer Tracing nor Spring Boot.
|
Thanks for the detailed explanation. From a "simple user" of these libs, it's very easy to get lost between the multiple existing libs, their feature overlap (but not quite), the deprecations, the compatibilities, the not quite stable yet libs, the ones compatible with specific versions of Spring Boot, the dying ones, the bridges etc etc. Your explanation brings a bit of clarity in this mess, thank you. I think we'll stick with Micrometer Tracing 1.1 until we're finally ready to migrate to Spring Boot 3.2 |
Please let us know if we can improve this in the Micrometer docs, we are appreciate feedback and happy to improve it. Unfortunately we can't really change the OTel docs so that it better calls out that OTel is not stable yet (I gave this feedback multiple times in the past). |
Will do :) |
When upgrading from v1.1.7 to v1.2.0, we get the following error at startup while using Spring Boot 3.1.5:
Stack Trace
However when using Spring Boot 3.2.0, the application starts fine.
Unfortunately we're unable to migrate to Spring Boot 3.2.0 yet which means we cannot use v1.2.0 because of this issue.
I'm wondering if this is a bug or if this break of compatibility is expected ?
Thanks a lot,
The text was updated successfully, but these errors were encountered: