[ot] Quartz ?

[Tom Zeller]

> Btw, that's even assuming we did use Quartz at all.  There's also the
> newer native Java executor service pool type of approach.  Quartz might
> be overkill for this honestly, unless we really do want to schedule
> certain maintenance things to run in a declarative way.  Most (all?) of
> our usage is the component instance-specific background task, and for
> that I honestly don't know whether Quartz is the best fit.  Need to
> think about it more.  Maybe it has applicability for the reloadable
> service stuff, not sure.

Agree. My thinking was if we're going to do the work of replacing
Timers, I would tend to reach for Quartz because it allows for more
advanced scheduling, meaning "update metadata everyday at 6am and 6pm
and if the job fails with a remote unavailable exception then
reschedule an hour later and email somebody". And that's overkill and
not really appropriate for things like replay detection.