Is there a reason why Exposed is (still) using joda-time?
06/01/2018, 7:59 AM
for jdk 1.6 compatibility, I think
06/01/2018, 8:16 AM
I know its being reworked to allow you to pick implementation
06/01/2018, 8:23 AM
Is it in progress ?
06/01/2018, 8:39 AM
Would be interesting to see the usage of pre-1.8 and 1.8+ 😉
06/01/2018, 9:38 AM
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
06/01/2018, 9:48 AM
Is it in progress ? or "just" on the roadmap ?
06/01/2018, 9:56 AM
I have prototype imlementation of such refactoring.