Use of command in docker mode could Autoconfigure the wrong bean

For both executor and docker mode, mesos.command is used. But the Executor TaskInfoFactory is triggered on mesos.command:
https://github.com/ContainerSolutions/mesos-starter/blob/master/spring-boot-starter-mesos/src/main/java/com/containersolutions/mesos/config/autoconfigure/MesosSchedulerConfiguration.java#L121

Hence, it's only by luck that the Docker TaskInfoFactory is instantiated, because the Executor version is valid because of the use of a mesos.command.