Enhancement: Allow run dates in the past, either optionally or by default

[RichardBradley]

Currently, if Quartz is started with a Trigger date for a Job that is in the past, it will fail to start with the following error:

Based on configured schedule, the trigger X will never fire.

This is controlled by the following code:

• https://github.com/quartz-scheduler/quartz/blob/a5c4d27e963f51097f9b2777489d310a88897ca4/quartz/src/main/java/org/quartz/core/QuartzScheduler.java#L852
• https://github.com/quartz-scheduler/quartz/blob/a5c4d27e963f51097f9b2777489d310a88897ca4/quartz/src/main/java/org/quartz/core/QuartzScheduler.java#L898

This is a problem for apps which wish to schedule a one-off job in the future. If the app is restarted after the job time has passed (and cloud based apps are often frequently restarted), then the app will fail to start.

I think it would be helpful for many users of Quartz if this behaviour were either turned off by default (which would increase the risk of users accidentally scheduling a job that will never run), or made configurable.

See also https://github.com/quartz-scheduler/quartz/issues/621 , an earlier issue with the same request

[lprimak]

This project is abandoned. See #1134