Bump jackson-databind to 2.13.2.2 via switching to BOM #10307
Merged
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.
Re-attempt #10302
Individual libs in Jackson don't necessarily all get released at the same time. The BOM is the right way to ensure versions are all on latest. In this case, to get a CVE patched within databind. See FasterXML/jackson-databind#3428 for more detail
This changes the
base
project to add a bit like aplatform
project in Gradle which recommends or enforces versions o dependencies for Jackson. Would like to gradually move away from the message subproject resolution hacking done currently.Unfortunately I can't find a nice way to set up the "expected versions" for the wars/jars right now. Normally the BOM has the same versions as the underlying pieces, so hopefully we go back there soon.