Exclude jackson3 artifacts coming in from citrus validation; current camel default is using jackson 2#2840
Merged
Merged
Conversation
…camel default is using jackson 2
oscerd
approved these changes
May 17, 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
2 participants
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.
We need to exclude jackson 3 artifacts coming in from citrus-validation-json - I'm trying to work out the errors in the camel-kamelet integration tests and I'm seeing issues with resolving the correct classes for datatypes and transformers in the protobuf tests. The issue is that the jackson 3 classes being on the classpath cause the camel-jackson3 versions of datatype/transformers to be resolved while the tests expect jackson 2.
When camel moves over to using jackson 3 as the default (apache/camel#21800) we can remove these exclusions.