We already have an api plugin for Jackson 3 https://plugins.jenkins.io/jackson3-api/
Afaik we don't use jackson in core ________________________________ From: [email protected] <[email protected]> on behalf of Ullrich Hafner <[email protected]> Sent: Tuesday, February 24, 2026 9:29 AM To: Jenkins Developers <[email protected]> Subject: Jackson 3.0 Another core library that we are using extensively in Jenkins is Jackson. There is a new major release with breaking changes available as well: https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.0 We use Jackson directly in core, plugins use it via the Jackson 2 API plugin. What are the plans here? Does it make sense to create a Jackson 3 API plugin so that plugins can migrate to Jackson 3 if they want? Or will this be a conflict when Jenkins core does not update its own dependency? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/0754AC9B-7A50-41AF-B0C0-06C424B92161%40gmail.com<https://groups.google.com/d/msgid/jenkinsci-dev/0754AC9B-7A50-41AF-B0C0-06C424B92161%40gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/PA1PPFD3E722C3AD0A4BF487D2C29222D7C8774A%40PA1PPFD3E722C3A.eurprd02.prod.outlook.com.
