Extra side-effects of Project.getTasksByName()?

[Lance (uklance)]

The plugin is already working much as you describe

No, it’s not. The fact that it’s using Set<String> and Set<Task> shows the problem.

Please read here for related topic

Multiple invocations of "allprojects {}"

This depends on how the plugin is written, it’s certainly possible to write plugins where order is important. Usually, Gradle provides an API such that you can code your plugin to work the same regardless of execution order. Let’s consider project.tasks which is an instance of TaskCollection, as with most of the collections in the Gradle model this extends DomainObjectCollection which has “live” methods including matching(Closure) and all(Closure). These will “Executes the given closure against…