The plugin configuration is evaluated at compile time, not when the task is run.\
This happens because the setOrElse(...) calls in the plugin class evaluate the otherwise lazily loaded properties.
I consider this a bug, given that the plugin supports configuring each property using lazy providers. It is especially annoying when running other Gradle tasks, which would then directly trigger issue #16.
The plugin configuration is evaluated at compile time, not when the task is run.\ This happens because the
setOrElse(...)calls in the plugin class evaluate the otherwise lazily loaded properties.I consider this a bug, given that the plugin supports configuring each property using lazy providers. It is especially annoying when running other Gradle tasks, which would then directly trigger issue #16.