4.1

Version 4.1

• Helper for using a version of the scheduler in unit/integration tests is now available in the artifact, through the class TestHelper.createManualScheduler(...). For usage example see SchedulerClientTest.
• It is now possible to manually trigger a check for due executions in the database. Of course, if this is done too frequently there will be an increased overhead.
• The scheduler can be instructed to do a best-effort attempt at executing executions it sees is being scheduled to run now() or earlier through the builder-method enableImmediateExecution().
• Bugfix: scheduler.getScheduledExecutionsForTask(...) was not working properly

4.0

Version 4.0

• Track number of consecutive failures of a task. For use in FailureHandler to avoid retrying forever, or retry with back-off.

Upgrading to 4.x

• Add column consecutive_failures to the database schema. See table definitions for postgresql, oracle or mysql. null is handled as 0, so no need to update existing records.

3.3

Version 3.3

• Customizable serlizer (PR #32)

3.2

Version 3.2

• Customizable table-name for persistence

3.1

Version 3.1

• Future executions can now be fetched using the scheduler.getScheduledExecutions(..)

3.0

Version 3.0

• New builders for task-creation, making it clearer what the config-options are. (See Tasks class and examples)
• Better default for failure handling for one-time tasks
• Enables recurring tasks to have data
• Schedule.getNextExecutionTime can now use all data from ExecutionComplete

Upgrading to 3.x

• No schema changes
• Task creation are preferrably done through builders in Tasks class

2.0

Version 2.0

• Possible to cancel and reschedule executions.
• Optional data can be stored with the execution. Default using Java Serialization.
• Exposing the Executionto the ExecutionHandler.

Upgrading to 2.x

• Add column task_data to the database schema. See table definitions for postgresql, oracle or mysql.