HDScanner start() ignores config property scanEnabled

The setter for the scanEnabled property does not cache the value, it only uses it to cancel an already-started scheduled task. If the setter is called during bean configuration, there is no scheduled task, the setter essentially becomes a no-op, and when start() is called the task is scheduled.

Effect is the only way to disable HDScanner via configuration is to remove the deployment; you can't leave it deployed but configure whether it is enabled (e.g. with a system property).