Since TASKMGMT-18, tasks module has a dependency to scheduler module, so we have a circular dependency: TASK => UI => SCHEDULER => TASK ...

Even the though this circle doesn't show up on CI (milestones, different scheduler version here), it does prevent the empty-webapp from starting, because scheduler is now expected, but not present.

The background story is that currently, scheduler module depends on magnolia-ui.
This is admittedly unfortunate —should be the other way around—, that's why we work around the circular dependency e.g. in AbstractCommandAction.

Therefore we need to apply the same workaround as in UI for now (and find proper degradation in case scheduler's not around).

// get quartz scheduler (same instance as scheduler module)
// due to creation of circular dependency, we can't simply import mgnl scheduler, yet we want to use same factory initialized scheduler in case someone customized it and we want to have all jobs in same group for monitoring purposes
Scheduler scheduler = (Scheduler) schedulerModule.getClass().getMethod("getScheduler").invoke(schedulerModule);