What is Quarkus team position regarding Quartz not being maintained anymore ?

[Olivier Masseau]

Hello,

We noticed that Quartz seems to not be maintained anymore/ CVEs not being fixed.

At least it is not very clear when looking at their Github :

https://github.com/quartz-scheduler/quartz/issues/839#issuecomment-1479458400

https://github.com/quartz-scheduler/quartz/issues/1134

What is Quarkus team position regarding this ?

Will Quarkus still support Quartz in the future or will it migrate to a new library ?

This is important for us as we would like to avoid any development using Quartz Schedulers (https://quarkus.io/guides/quartz) not being sure if it will still be supported.

[Martin Kouba]

Hello Olivier,

if you don't need persistent tasks or clustering then quarkus-scheduler
is a viable option. It's a lightweight in-memory scheduler implementation.

For more advanced scheduling use cases, you might consider other
alternatives. For example, there is a jobrunr Quarkus extension [1].
Unfortunately, it does not seem to support the existing Quarkus API
(@Scheduled etc.).

Martin

[1]
https://www.jobrunr.io/en/documentation/configuration/quarkus/

> --
> You received this message because you are subscribed to the Google
> Groups "Quarkus Development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to quarkus-dev...@googlegroups.com
> <mailto:quarkus-dev...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/quarkus-dev/31858bed-cc25-42fe-8177-65fcc57b5f02n%40googlegroups.com <https://groups.google.com/d/msgid/quarkus-dev/31858bed-cc25-42fe-8177-65fcc57b5f02n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Sven Boeckelmann]

you also may want take a look at jobrunr
https://www.jobrunr.io/en/documentation/configuration/quarkus/