Clean up some jackson dependency excludes by moving it to top level pom#18190
Merged
capistrant merged 1 commit intoapache:masterfrom Jul 2, 2025
Merged
Conversation
This file contains hidden or 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
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.
Description
follow on to #18013. It was pointed out, after merge, that I should have consolidated the excludes for two of the jackson libraries in the root pom instead of adding one off to every module that needed it. This aims to rectify that mistake. It also found another location where comments called for removing an explicit snakeyaml version pin in a module once jackson got upgraded.
Release note
N/A
Key changed/added classes in this PR
pom.xmlThis PR has: