Skip to content

Conversation

plumstone
Copy link

@plumstone plumstone commented Apr 28, 2025

Fixes #60

This PR is a proposal for a long-term solution for the continuous maintenance of the jackson-databind library.

The user of jackson-databind-nullable will be forced to explicitly declare the dependency on jackson-databind. This gives him full control over the jackson version he uses for his project.

In the past, jackson-databind has been known to have some vulnerabilities.
With this change, the consumer is no longer directly bound to the jackson version that jackson-nullable was built with.

If you have any concerns, please let me know. I welcome any feedback.

README.md Outdated
@@ -25,6 +25,30 @@ The module is compatible with JDK8+

## Usage

Starting from version `2.0.7` the jackson-databind dependency is no longer transitively shipped with this library. Therefore, it needs to be declared explicitly. This enables you to be more flexible in updating the jackson version you are using for your project.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor typo - I think it should be "version 0.2.7" instead of "version 2.0.7" :)

@Maran23
Copy link

Maran23 commented Aug 22, 2025

I think this is a good idea. This need to be documented when it is merged in the release notes / changelog.
Consumers will notice if the jackson dependency need to be added explicitly as well.

@plumstone plumstone changed the title Change jackson-databind dependency to not being shipped transitively (OpenAPITools#60) Change jackson-databind dependency to not being shipped transitively Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade jackson-core to latest. Is this repo still maintained ?
3 participants