build: Use only one jackson version #10795
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
timyates
approved these changes
May 3, 2024
There was a problem hiding this comment.
For anyone interested, this split to have 2 managed versions was added here
Because Jackson ended up with different version numbering for core, bom and databind
FasterXML/jackson-databind#3428 (comment)
Going back to a single version however is the correct route to take now there is agreement inside jackson as renotave doesn't know these should be aligned so we keep ending up with different versions...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close: #10745
Use
managed-jacksonversion everywhere.Use
managed-jackson-databaindshould be removed in Micronaut Framework 5.