+1 due to the fact that we just used it to support cron-expressions (there was no other explicit reason). however, we have to keep it as an optional dependency and delegate to it once it's on the classpath, because some users use Scheduler#unwrap for more advanced cases.
regards, gerhard 2018-01-05 17:39 GMT+01:00 Mark Struberg <[email protected]>: > Hi folks! > Since I've now had a few complaints about Quartz 'phoning home' (totally > useless update check), I'm really inclined to just kick out quartz and > implement the Scheduler ourselves. > Implementing a proper Scheduler is not that complicated anyway, so do we > like to roll this ourselves? > Or do you think I underestimate the effort? > > LieGrue,strub >
