Skip to content

Jackson 3.x #5806

Description

@ndr-brt

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.

Activity

  1. added
    feature_requestNew feature request, awaiting triage
    triageall new issues awaiting classification
    on Jun 9, 2026
  2. added this to the 1.0.0 milestone on Jun 9, 2026
  3. github-actions commented on Jul 8, 2026

    @github-actions
    Contributor

    This issue is stale because it has been open for 28 days with no activity.

  4. removed
    staleOpen for x days with no activity
    triageall new issues awaiting classification
    on Jul 8, 2026
  5. ndr-brt commented on Sep 2, 2026

    @ndr-brt
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature_requestNew feature request, awaiting triage

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions