-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade jackson related packages #446
Conversation
|
The only build failure is on ksql downstream validation and it is spot bug:
|
Known spot bug error in ksql:
|
Jackson was bumped upstream: confluentinc/common#446 Version 2.13 returns null instead of NullNode (cf FasterXML/jackson-databind#3389)
Jackson was bumped upstream: confluentinc/common#446 Version 2.13 returns null instead of NullNode (cf FasterXML/jackson-databind#3389)
Jackson was bumped upstream: confluentinc/common#446 Version 2.13 returns null instead of NullNode (cf FasterXML/jackson-databind#3389)
…9070) Jackson was bumped upstream: confluentinc/common#446 Version 2.13 returns null instead of NullNode (cf FasterXML/jackson-databind#3389)
<dependency> | ||
<groupId>com.fasterxml.jackson.core</groupId> | ||
<artifactId>jackson-databind</artifactId> | ||
<version>${jackson.databind.version}</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd missed this during the original changes, sorry about that. We really shouldn't be adding individual jackson modules to the common pom. The whole point of using the bom is to only have that one place where these are defined. Otherwise all future updates need to update both the bom and these.
We should just remove all version properties and dependencies other than the bom version.
No description provided.