Fail to configure projects with `tasks.whenTaskAdded` about dependency-analysis-gradle-plugin HOT 4 CLOSED

The use case is that we want to execute the task downloadStrings before a stand alone app is assembled. The normal tasks.named doesn't work because the task that we are looking for doesn't exist yet.

You can use afterEvaluate for this case. That won't eagerly realize all your tasks. Or even better, tasks.withType().matching { /* check name here */ }. If you're on Gradle 8.6, you can use tasks.named { ... } and that is lazy.

from dependency-analysis-gradle-plugin.

Could you try this again with the latest snapshot? I wonder if this relates to #1115, which is fixed now.

from dependency-analysis-gradle-plugin.

Nevermind, I can reproduce this easily in a test.

Although, what is your use-case for using whenTaskAdded? Looking at the javadoc, I'd say it's a bad practice, as it realizes all tasks in a project.

from dependency-analysis-gradle-plugin.

tasks.whenTaskAdded {
    if (name.startsWith("generate") && name.endsWith("Assets")) {
        dependsOn("downloadStrings")
    }
}

Last week I saw on our scans that we were creating a lot of tasks con configuration on the tasks that use that and we are looking for a way to remove them.

The use case is that we want to execute the task downloadStrings before a stand alone app is assembled. The normal tasks.named doesn't work because the task that we are looking for doesn't exist yet.

from dependency-analysis-gradle-plugin.