Issue with jackson library after upgrade to 2.19.0 as dependabot suggested #274
Replies: 4 comments
-
Please provide a description of the issue. |
Beta Was this translation helpful? Give feedback.
-
@juanroldan1989 I've reported this to GitHub. I hope your Jackson 5 joke that you've edited was at least funny to you. |
Beta Was this translation helpful? Give feedback.
-
I've added a full description of the issue. I apologise for the joke, it was not funny, but the issue is real and it happens when upgrading to the latest version of the library, hopefully it will save someone else's a couple of hours of debugging. Dockerfile for our Java application has base image: |
Beta Was this translation helpful? Give feedback.
-
Without having any other information than what is presented, I'd guess you have older (pre-2.19) version of implementation "com.fasterxml.jackson.core:jackson-annotations:2.19.+" not sure why this would be needed, TBH, since If possible, it'd probably make sense to depend on Jackson BOM ( |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Dependabot requested we upgrade to the latest Jackson library in one of our Java applications:
But we had to roll it back because it was not working with Open API and the Actuator endpoint.
Therefore our application running in ECS was failing because the health-checks in our Target Groups pointing to the actuator endpoint was failing. The Java application itself was running fine, the actuator endpoint was failing with "No such method" error, which made it even harder to find out why our application was crashing.
Hopefully this is useful to anyone upgrading to the latest jackson library version.
Beta Was this translation helpful? Give feedback.
All reactions