I was trying out the new Spring Boot 4.0.0-RC2 release and noticed that quartz was throwing exceptions. After a little search i found this issue that was already raised https://github.com/quartz-scheduler/quartz/issues/1407. it looks like quartz 2.5.1 is not usable with a postgres database. so this is just a heads up that you might want to skip that version of quartz.
Comment From: wilkinsona
Thanks for the heads-up and for trying RC2. There are various bug fixes, regression fixes, dependency upgrades, and a feature in Quartz 2.5.1. While it sounds like this won't suit PostgreSQL users, they will be of benefit to those using other databases. As such, I don't think we should downgrade. Instead, we'll pick up a fix for https://github.com/quartz-scheduler/quartz/issues/1407 once it's available.
Comment From: LeosBitto
Prioritising new features against stability makes sense for the release candidates of 4.0, but somehow the upgrade to Quartz 2.5.1 with its known bugs got into 3.5.8 as well - was this intentional or just a mistake?
Comment From: bclozel
@LeosBitto Andy explained the situation well just above: this quartz release also fixes bugs and regressions. While this is clearly an inconvenience for postgresql users, other developers might rely on important fixes.
We usually downgrade if the feature is broken for the majority of developers or the maintainers declare that version as broken themselves. You can help with the swift resolution of the situation by testing the proposed fix or assisting the maintainers. Our next maintenance release date is already scheduled; as far as I understand the fix is not in yet. In the meantime you can override the quartz version in your application.
Thanks!