Right now it's not intuitive to developers that jobs configured on the system execute with the system instance not the task driver instance.
[x] Move the ConfigureSystemJob...() methods off the AbstractTaskDriver instance and place it on the system instance.
[x] Expose the task driver system instance to the AbstractTaskDriver instance.
This better matches the pattern used for scheduling off of other task drivers (Ex: subtaskDrvier.Configure....()) and clearly identifies that the task driver instance is not the one controlling the scheduling order.
Right now it's not intuitive to developers that jobs configured on the system execute with the system instance not the task driver instance.
ConfigureSystemJob...()methods off theAbstractTaskDriverinstance and place it on the system instance.AbstractTaskDriverinstance.This better matches the pattern used for scheduling off of other task drivers (Ex:
subtaskDrvier.Configure....()) and clearly identifies that the task driver instance is not the one controlling the scheduling order.