Re: [jackson-dev] Evolving thoughts on Java baseline: Jackson 2.9 still with Java 7; 3.0 with Java 8?

It might be better to create a Wiki page for Jackson project, although perhaps we could do both: issue(s) for discussion, Wiki page as a draft document of current thinking. -+ Tatu +- On Tue, Oct 25, 2016 at 7:17 AM, Lovro Pandzic wrote: > Can we formalise all of this

Re: [jackson-dev] Evolving thoughts on Java baseline: Jackson 2.9 still with Java 7; 3.0 with Java 8?

Can we formalise all of this in form of github issues? FYI JSON B public draft (https://java.net/projects/jsonb-spec/pages/Home) contains some pretty good insight in terms of Java 8 Time/Date/Optional handling etc. (no parameter names module functionality though). On Tuesday, October 18, 2016

Re: [jackson-dev] Evolving thoughts on Java baseline: Jackson 2.9 still with Java 7; 3.0 with Java 8?

Ah ok. Just wanted to make sure as it makes a big difference. :) There would still be room for plenty of discussion on exact changes to make, limits and so on. -+ Tatu +- On Tue, Oct 4, 2016 at 10:39 PM, Christopher Currie wrote: > Sorry, editing mistake, that should

Re: [jackson-dev] Evolving thoughts on Java baseline: Jackson 2.9 still with Java 7; 3.0 with Java 8?

Sorry, editing mistake, that should have been *not* necessary, and in fact not desired. StringTemplate 4 changed co-ordinates as a patch release (from 4.0.2 to 4.0.3) causing headaches in class paths and eventually needing to use the dependency plugin's "banned dependencies" feature. On Tue,

Re: [jackson-dev] Evolving thoughts on Java baseline: Jackson 2.9 still with Java 7; 3.0 with Java 8?

I think that if Jackson doesn't take the opportunity to cull the dead API weight at version 3, it will never happen. I support the proposal to make the Java 8 update in version 3, and shed the API as needed. I also agree that changing the Maven co-ordinates is necessary. Christopher On Tue, Oct