Jackson 3.x #5806
Copy link
Copy link
Labels
feature_requestNew feature request, awaiting triageNew feature request, awaiting triage
Milestone
Description
Activity
- addedfeature_requestNew feature request, awaiting triageNew feature request, awaiting triagetriageall new issues awaiting classificationall new issues awaiting classification
on Jun 9, 2026 This issue is stale because it has been open for 28 days with no activity.
- addedstaleOpen for x days with no activityOpen for x days with no activity
on Jul 8, 2026 - removedstaleOpen for x days with no activityOpen for x days with no activitytriageall new issues awaiting classificationall new issues awaiting classification
on Jul 8, 2026 - added a sub-issue
on Jul 29, 2026 our blocker here is Jersey.
The Jackson 3 support has been requested and implemented, so it will likely be part of the next release.We could also switch by providing our custom reader/writer but the effort is not justifiable, so let's wait for them.
Metadata
Metadata
Assignees
Labels
feature_requestNew feature request, awaiting triageNew feature request, awaiting triage
Feature Request
Jackson 3.x has reached some maturity (3.2 was released yesterday), I would propose to jump on it before going 1.0.0 ourselves.
There are some major changes in groupIds and package names, so all the work starting from RuntimeMetamodel through GradlePlugins, Connector, IdentityHub and the Technology repos need to be done in sync (as we don't have separate branches).
Migration guide
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
Are there any requirements?
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Solution Proposal
If possible, provide a (brief!) solution proposal.