This message was deleted.

why would you add it conditionally? wouldn't it be easier to execute it conditionally instead?

This would be the workaround. But it would be cleaner not to create it at all (and it is less confusing in the task list in the ide)

How would the property be provided? Because you can simply read the property during the configuration phase and wrap the

tasks.register

call inside an if block:

if (property) {
    tasks.register<MyTask>("myTask)
}

Yeah, but this requires evaluating the Property by calling get(). The user should set a value of type Property and based on this value I will create the tasks.

in that case you'll require an

afterEvaluate

I think

This is exactly I want to prevent :D In theory it should be possible by simple passing a transformer here: https://github.com/gradle/gradle/blob/836be3907064dec84acf62815c120d950bca77fd/subprojects/core/src/main/java/org/gradle/api/internal/tasks/DefaultTaskContainer.java#L416

https://github.com/gradle/gradle/blob/836be3907064dec84acf62815c120d950bca77fd/sub[…]in/java/org/gradle/api/internal/tasks/DefaultTaskContainer.java I mean, clearly gradle doesn't want you to do that, so I'm sure they have a reason 🤷

Gradle needs to build a task dependency tree (after configuration stage) before it even begins executing tasks. How would a property, that you expect to be evaluated at execution time, influence the task tree which is built at configuration time? 🤔

Properties (or Providers) are evaluated during configuration time, otherwise you can't configure your build. You can also use

addLater

for dependencies though.

Yes you can evaluate providers whenever. But I’m taking

Yeah, but this requires evaluating the Property by calling get().

to mean that you don’t want to evaluate it at configuration time?

Yes, I don't want to call get() explicitly by myself. Instead, you should use

set

and let Gradle handle calling

get

to lazy configure your build.