Is there a reason why Exposed is (still) using joda-time?

for jdk 1.6 compatibility, I think

I know its being reworked to allow you to pick implementation

Is it in progress ?

Would be interesting to see the usage of pre-1.8 and 1.8+ 😉

Yep, it's on our roadmap. We want to allow to choose among joda/java.time/java.time-backport with just changing the dependency, but before that we plan to split Exposed to core+dialects jars and make it modular and extendable

Is it in progress ? or "just" on the roadmap ?

I have prototype imlementation of such refactoring.