Jackson 2.13.0 released, see https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.13

[Tatu Saloranta]

As per title, I finally managed find time to wrap up 2.13 release so
have the full set of 2.13.0 standard Jackson components out.
Changes are outlined on 2.13 release page:

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.13

and I earlier blogged a bit about what is included here:

https://cowtowncoder.medium.com/sneak-peek-at-jackson-2-13-6f3009ce2d79

TL;DNR:

- This is more of a bug-fix release after big-ticket 2.12 -- but with
about 100 fixes, new features across all components
- TOML format support! (jackson-dataformat-toml)
- Added support for "Jakarta" variant APIs (over old "Javax" like
"JAXB") -- for JAX-RS, JAXB, JSON-P
- JDK baseline for most components upgraded to JDK 8
(jackson-annotations, streaming (jackson-core), jackson-jr remain at
JDK 6 minimum for this release at least)

Thank you everyone who helped get this release done, completed.

As usual, please report any and all regressions,

-+ Tatu +-

[Nakamura]

Hey Tatu,

This is pretty minor, but https://github.com/FasterXML/jackson-databind/commit/765e2fe1b7f6cdbc6855b32b39ba876fdff9fbcc was a breaking change as far as jackson semantics, so it would have been nice to include it in an RC.  It broke one of our tests that had used ObjectMapper as a shorthand for an unserializable object.

Otherwise, we're excited about adopting the new version, thank you!!

Thanks,

Moses

--
You received this message because you are subscribed to the Google Groups "jackson-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jackson-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/CAL4a10h4o1ScFg1-SAT80Dx5%2B6SgJFK8xAJ9G5827_XJnHuTVQ%40mail.gmail.com.

[Tatu Saloranta]

On Fri, Oct 15, 2021 at 9:40 AM Nakamura <nny...@gmail.com> wrote:
>
> Hey Tatu,
>
> This is pretty minor, but https://github.com/FasterXML/jackson-databind/commit/765e2fe1b7f6cdbc6855b32b39ba876fdff9fbcc was a breaking change as far as jackson semantics, so it would have been nice to include it in an RC. It broke one of our tests that had used ObjectMapper as a shorthand for an unserializable object.

Just to make sure I understand the previous behavior here: did attempt
to serializer `ObjectMapper` result in `StackOverflowError`?

I think I will create a new issue, marked as fixed, to cover
undocumented part of the change (documented part being ability to
serialize
JsonProcessingExceptions), mark as fixed for 2.13 & add in release notes.

Thank you!

-+ Tatu +-

> To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/CAEYWR9uy6ROEeLT%3DggoGs_67zL2oRdQKsPmZzArG7nVn_kccAQ%40mail.gmail.com.

[Tatu Saloranta]

On Fri, Oct 15, 2021 at 10:27 AM Tatu Saloranta <ta...@fasterxml.com> wrote:
>
> On Fri, Oct 15, 2021 at 9:40 AM Nakamura <nny...@gmail.com> wrote:
> >
> > Hey Tatu,
> >
> > This is pretty minor, but https://github.com/FasterXML/jackson-databind/commit/765e2fe1b7f6cdbc6855b32b39ba876fdff9fbcc was a breaking change as far as jackson semantics, so it would have been nice to include it in an RC. It broke one of our tests that had used ObjectMapper as a shorthand for an unserializable object.
>
> Just to make sure I understand the previous behavior here: did attempt
> to serializer `ObjectMapper` result in `StackOverflowError`?
>
> I think I will create a new issue, marked as fixed, to cover
> undocumented part of the change (documented part being ability to
> serialize
> JsonProcessingExceptions), mark as fixed for 2.13 & add in release notes.

Created and closed

https://github.com/FasterXML/jackson-databind/issues/3302

and added a brief mention in 2.13 release notes. Thanks again!

-+ Tatu +-

[Nakamura]

I'm not 100% sure, but that's my guess. I'm now instead using a purpose-built self-referential value to run the test instead.

To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/CAL4a10iJYN_opcb1VOXO5B6FsX2rDTjAsi9OFpve-FbEWOBgwg%40mail.gmail.com.