-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
http-client throws NoSuchMethodError 'boolean com.fasterxml.jackson.core.io.NumberInput.looksLikeValidNumber(java.lang.String)' #10745
Comments
I am hoping this will go away once this pull request gets merged: #10749 |
Close: #10745 Use `managed-jackson` version everywhere. Use `managed-jackson-databaind` should be removed in Micronaut Framework 5.
#10795 is to use 1 jackson version in micronaut 5. What about micronaut 4? With micronaut-platform 4.4.1, jackson-databind still uses different version than other jackson dependencies. Would that be fixed with micronaut-platform 4.5.x? |
@ethanhere No. that it is not so. That PR will make sure we will use 2.17.0 everywhere. We will release that in Micronaut Core 4.4.9 which will be released in Micronaut Platform 4.4.3. |
any idea when Micronaut Platform 4.4.3. would come out? |
we are releasing Micronaut Platform 4.4.2 today. Typically, 7 - 10 days after we will release the next patch. A workaround is to force the Jackson Databind version to 2.17.0.
Or you can force core to 4.4.9 once we release it. |
This should be fixed in Micronaut Framework 4.4.3 |
Expected Behavior
I tried to upgrade the platform from 4.3.8 to 4.4.0. When doing so, a few tests using Jackson serialization threw the
NoSuchMethodError
error.Looking at the
micronaut-core-bom-4.4.3.pom
I noticed that Jackson Databind and Jackson Core have different versions:Since Databind depends on Core, their versions usually go hand in hand. Any particular reason why this happened?
Actual Behaviour
Here's the stacktrace:
Steps To Reproduce
No response
Environment Information
Windows, JDK 17
Example Application
No response
Version
4.4.0
The text was updated successfully, but these errors were encountered: