[Feature] Support Jackson 3.x release line

[reta]

Feature Description

Jackson has released major new 3.x version [1], this is major breaking change [2] comparing to 2.x release line, including both package and artifact changes.

[1] https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.0
[2] https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-1

Use Case

Swagger tightly integrates with Jackson in core (not to mention other components) and it may not be possible to support both versions (2.x and 3.x) at the same time.

Suggested Solution (optional)

Thinking about possible options, having new Swagger 3.x release line would be probably the best way to move forward.

Alternatives Considered

Support both versions (2.x and 3.x) at the same time. It may not be possible, or otherwise maintainable.

Additional Context

Checklist

• I have searched the existing issues to ensure this is not a duplicate.
• This feature would be useful to more than just my use case.
• I have provided enough detail for the maintainers to understand the scope of the request.

[nnam-droid12]

Thanks for opening this, @reta this seems like a significant upcoming change since Jackson 3.x introduces breaking API differences.
I’m following this discussion with interest; if the maintainers decide to move forward, I’d be happy to help with testing or migration work.

[reta]

Thanks a lot @nnam-droid12 , I would love to get guidance from maintainers before doing any work there

[nnam-droid12]

Sounds good @reta . I’ll keep an eye on this as well. Once the maintainers share their guidance on the preferred approach for Jackson 3.x support, I’d be happy to work along side you with implementation or review if needed.

[bnasslahsen]

+1, this is also needed for springdoc-openapi project since Spring-Boot-4 has fully transitioned to Jackson 3 as its primary implementation.

It would be great to see Swagger Core adopt the modern Jackson version as well!

[vpelikh]

Is anyone already working on this issue?

[reta]

Is anyone already working on this issue?

Not yet, it would be great to get +1 from maintainers before investing time

[yuanjinyong]

Is there any progress?

[vpelikh]

Is there any progress?

Yep, I just committed the changes with jackson 3 to #5031.
There were too many changes, so I'll probably clean up the PR later.