Does this mean you get the same result adding a task to it or that an already existing task in the plugin has this behaviour?
While trying to understand why the tasks I developped in my own plugin was executed twice, I tested an existing task in the Chat plugin and it executed twice too.
I tested some tasks from other plugins too but can’t remember which ones. Some where executing once but there was nothing obvious about the difference of implementation.
Maybe there is something to do with the autoloading?
On a fresh plugin, the engine contains this line:
config.autoload_paths << File.join(config.root, "lib")
If I don’t autoload lib but lib/some_path to avoid autoloading lib/tasks, it seems better, but the downside is that it breaks autoloading (I stopped here). Which may lead to have a bunch of require_relative statements to compensate…