This message was deleted.

you can wrap it in a

withPlugin

block: https://docs.gradle.org/current/dsl/org.gradle.api.plugins.PluginManager.html#org.gradle.api.plugins.PluginMana[…]g.String,%20org.gradle.api.Action)

I think I want to achieve too much 😅. My goal was:

tasks.register("myTask") {
    // apply the plugin
    
    // configure the plugin
    
    // run the task from the plugin
}

why would you use a task for the application/configuration of another plugin? you're mixing the configuration and execution phases of gradle

Yep 😕. What I wanted to achieve is to have a plugin that will be run only sometimes (basically the dependencies version check). So I don’t want to waste build time to apply and configure this plugin for every build if it is going to be used once in a while.

If it's a well-behaved plugin, it shouldn't incur must of an extra cost, so I wouldn't worry about it too much. gradle is very good with avoiding work if it can.

Great, thanks for explaining that! I admit I started worrying about it before even checking if it matters for the build time 😉 (and probably doesn’t matter as you suggest).