Plan to raise minimum JDK requirement for Jackson 2.14 from JDK 6 to JDK 8 for all components

[Tatu Saloranta]

The minimum JDK one can use Jackson on has been JDK 8 for most
components since version 2.13 (and minimum JDK to build anything has
been JDK 8 as well).
Exceptions include:

* jackson-core, jackson-annotations only require (in theory) JDK 6

But even with that goal, there have been accidental uses of things
like `java.lang.Objects` methods that are not present on JDK 6. We do
not have a good regression test suite to guard against that.

It has been proposed that we should now raise the baseline to Java 8
for ALL components, including streaming (jackson-core) and annotations
(jackson-annotations).
This would occur for Jackson 2.14: we would keep the last
"pre-all-Java8" branch -- 2.13 -- open for longer for those users that
cannot (yet) upgrade to Java 8 platform.

When this was proposed on "jackson-dev" mailing list, no concerns were
voiced, so perhaps this is not controversial proposal.

But I wanted to send this to a bit larger audience to let everyone
voice their concerns.

So: anyone concerned with the move to require Java 8 (JDK 8) for all
Jackson 2.14 components (and forward)? Note that we will still need to
be careful with some usage, to allow Jackson use on platforms like
Android.

-+ Tatu +-

[Mantas Gridinas]

No concerns here.

Though, with advent of containerized CI, wouldn't it be as simple as running the same test suite in some flavor of JDK 6 image to test for earlier JDKs regressions?

--
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/CAGrxA24GZpuznJpfD9SqMsshUJTn%2B%3D2y0RaekFeGBkaM%2B6BSqg%40mail.gmail.com.

--

// Mantas

[Tatu Saloranta]

On Wed, Apr 20, 2022 at 12:09 PM Mantas Gridinas <mgri...@gmail.com> wrote:
>
> No concerns here.
>
> Though, with advent of containerized CI, wouldn't it be as simple as running the same test suite in some flavor of JDK 6 image to test for earlier JDKs regressions?

True, although it used to be the case that one needed specific support
by providers like Travis, and they started dropping support for
earlier JDKs.
This may have changed, but at the same time there is the diminishing
return on time invested at this point.

-+ Tatu +-

> To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/CAE9hW8Rj7EWT2fzsjdARU9RV9d0AvPDSLAz_c%2Bc1%2BdHSU4S%3DDw%40mail.gmail.com.