Your only real option is to advance the system's time before starting the scheduler.
You'll get strange results if you advance the time while it is running. (actually, probably not too strange - may just cause a lot of trigger misfire handling, etc. ). – jhouse Jun 7 at 19:28 Advancing system time also potentially leads to a lot of misfire handling, but that's exactly what I want.
I'd appreciate a solution that wouldn't require messing with system time as it's not exactly under control of the application... – schmeedy Jun 8 at 13:04.
I'll just highlight the solution we ended up implementing for other people that might be interested. In the end, we did not use Quartz in the development environment at all. Scheduler is only running in the production configuration (where it's obviously not possible to shift time).
Then we have a special piece of code that launches daily processing for every day when shifting time (which is only present in development / test environment). The bottom line for us: don't try to combine scheduler & moving time into the future - create separate configuration with one XOR another with special logic to replace scheduler in the scheduler-less configuration.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.