fix: bump jackson-databind to 2.21.0 in junit-sample#5
Merged
outofcoffee merged 1 commit intoMay 27, 2026
Merged
Conversation
This was referenced May 27, 2026
952d065 to
5c73293
Compare
outofcoffee
added a commit
that referenced
this pull request
May 27, 2026
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.
Aligns the junit-sample's direct
jackson-databinddependency with the Jackson version current Imposter releases are built against, so the example's runtime classpath uses a single, consistent Jackson.Summary
jackson-databindfrom 2.18.2 to 2.21.0 injunit-sample/pom.xmlImplementation details
Imposter publishes against Jackson 2.21.0. The sample's direct
jackson-databinddeclaration was the nearest match in Maven's nearest-wins resolution, so it kept pullingjackson-annotations2.18 onto the test classpath. That conflicted withjackson-module-kotlin2.21 (which callsJsonProperty.isRequired()expecting the newOptBooleanreturn type introduced in 2.19+), producingNoSuchMethodErrorat engine startup and breaking theExamplesjob in imposter-jvm-engine's CI. Bumping the sample's direct version to 2.21.0 lets nearest-wins agree with Imposter on a single Jackson version.The example's
PetService.javausesObjectMapperfromsrc/main/java, so the dependency itself must stay (compile-scope) — only the version needs to track the engine.