DbSchedulerAutoConfiguration - Configured Tasks Non Null Check

[he-eric98]

I was exploring db-scheduler in general for a spring-boot app and I noticed the following check:

this.configuredTasks = Objects.requireNonNull(configuredTasks, "At least one Task must be configured");

however, I think this doesn't do what was intended - when I started my app up without any Tasks configured (I dove head first in skimming the docs), the list was just empty instead of null.

The message "At least one Task must be configured" led me to think this should probably throw an exception when the list is empty instead of if the list is null

was hesitant to file an issue because I wasn't sure if there is a use-case for running with 0 configured tasks or maybe there is something else I am not aware of