My vote is to absolutely move up to Java 8 as the minimum. Caveat: I don't do Android or anything that is shackled to old Java versions.
-Drew On Saturday, December 5, 2020 at 4:06:49 PM UTC-5 Tatu Saloranta wrote: > Ok so something to consider for eventual Jackson 2.13 (as per my > earlier note, I don't plan on starting that until January and after > 2.12.1 is done): should we finally increase JDK requirement for > `jackson-databind`? > I will start this thread to give everyone a chance to chime in over > next month or so: no decision will be made until January 2021. > > I propose that Jackson 2.13 would require Java 8 for components other > than annotations and streaming API (which do not really benefit much). > This would have main benefits of: > > 1. Allow bundling of Java 8 datatypes (Optional), parameter name > access (for auto-detecting Creators) -- similar to Jackson 3.x > 2. Allow API improvements in 2.x to get yet closer to 3.0 > compatibility (could backport couple of missing closure-based > configuration methods) > 3. Overall API improvements for configuration: passing handlers as > closures is useful > > In addition, version 2.12 would become Long-Term Support version so > there should be updates beyond security patches for at least 2021, > maybe longer if there is demand (and conversely 2.10 and 2.11 would > have more limited timespan). > > I assume that most users are already on Java 8 but I think I would > like to hear from those who are not; and whether there are specific > concerns for, say, Android users. > > -+ Tatu +- > -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/afba2eea-6dad-42fb-acfc-83c9cfd55e4fn%40googlegroups.com.
