Tatu Saloranta

Thank you @gsmet !

Ok after couple of small tweaks (figuring out dir ref to GraalVM etc), got build going. So I think this is fine. **EDIT**: and after building, running service with given...

@gsmet Trying to work on this again, now that 2.19.0 is released. Noticing that I can only build against 2.18.*; attempts to building against 2.19(.0) fail due to one thing...

Quick note: been investigating this, learning much more about the challenges. There are multiple ways to (try to) achieve this, f.ex: 1. Reduce introspection of accessors at low-level, for JDK...

Ok some incremental progress, for 3.0 (.0-rc5): now for deserialization side, full introspection is avoided for deserialization of "well-known" types (ones for which Jackson or modules has explicitly registered deserializer)...

Phew! I figured out how to order things to avoid Method introspection for serialization of explicitly supported types: as I mentioned earlier this is for 3.0.0. Will mark this as...

@gsmet Given that work to re-order things is based on working around specific type (`java.sql.Date` in this case), there are likely other paths that would still trigger same issue. So...

Was implemented for 3.0.0-rc5.

Ok. that PR did produce imports according to the style guide, as far as I could see. So cautious +1 for this.

Yes and no: yes, they definitely should have included checked `IOException` in 2.x. My mistake, but unfortunately can't change (which you did not suggest I know, just mentioning for readers'...