Note: Jackson 2.x and Jackson 3.x can exists in parallel They both package jackson-annotations but with different version
Jackson 2.20 (our current version) package jackson-annotations:jar:2.20 Jackson 2.21 (next version, LTS apparently) package jackson-annotations:jar:2.21 Jackson 3.0 package jackson-annotations:jar:2.20 Jackson 3.1 (our current version) package jackson-annotations:jar:2.21 If a plugin depends (direct or transitive) different jackson-annotations can cause upper bound issue. But apparently PCT discovered also java.lang.ExceptionInInitializerError: Exception java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonSerializeAs When updating to Jackson 2.21 I cannot reproduce the issue (with Junit plugin for example) So if bom https://github.com/jenkinsci/bom/pull/6432 pass I would suggest to upgrade to Jackson 2.21.1 We would need to keep jackson-annotations aligned if they change On Sunday, March 1, 2026 at 9:08:22 AM UTC+1 Valentin Delaye wrote: > Plugin transition will take some time but already happen. > > Example is flyway-api that will require jackson3 because the upstream > dependency now require it ( > https://documentation.red-gate.com/fd/release-notes-for-flyway-engine-179732572.html > ) > > Cheers, > > On Tuesday, February 24, 2026 at 10:01:10 AM UTC+1 [email protected] wrote: > >> 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]. >> 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/a24c392f-d485-44f6-9419-8e6228428402n%40googlegroups.com.
