This message was deleted.

No, mainly the cross-project configuration is bad. Collecting information should be ok I think. But on the other hand, things like

dependencies { implementation subprojects[0].tasks.someOtherJar }

are very bad, even worse than cross-project configuration

the next I do in custom plugin is actually

custom task ...

dependsOn(subprojectsTasks)

but this is not a

dependencies {}

. This custom plugin and custom tasks are supposed to be running occasionally. I believe, your example means smth different. In my case, there is no project dependencies obtained this way. But here is a custom task that should depend on subprojects' tasks given by name.

Even for collecting information you break project isolation right?

I'm doing this for "aggregation": i need to run a task that would depend on every subproject's particular task

What you are doing should be done like the new test aggregator plugin does but I would like to see a really tiny example of it, I asked some time ago but I got no reply I think

I don't think the test aggregation plugin pattern applies, as he does not want to get reports or other ouptut from these tasks. Afair just for

dependsOn

it might be fine.

my custom task depends on subprojects' tasks only to enforce running them in order. So, my custom task is kind of "lifecycle" task. It doesn't use any output, because subprojects' tasks would generate all input I need themselves.

running ktLintCheck already runs it in all subprojects

ok but my question is how to make my custom tasks

what is your task doing

running all tasks for the specified name for all subprojects

what custom tasks? If you run

gradlew ktLintCheck

, Gradle searches for this task in all projects and executes them. If you run

gradlew :ktLintCheck

it only runs it in the root project. So what Javi meant is, that you don't need to add a lifecycle task just to run the same-named task in all subprojects

by depending on them

btw, if you say that depending on subprojects' tasks OUTPUTS is bad - is there any good way to depend on outputs?

I just gave you the link

makes sense

Vampire [14:18 Uhr] https://docs.gradle.org/current/userguide/cross_project_publications.html

If you run

gradlew ktLintCheck

, Gradle searches for this task in all projects and executes them.

If you run

gradlew :ktLintCheck

it only runs it in the root project.

this works from CLI but what if I would like to run a task, that would involve subprojects' tasks?

root build.gradle

tasks.register("staticAnalysis") {
    dependsOn(tasks.named("ktlintCheck"))
}

i believe (and I actually observe) that this won't run

ktlintCheck

for each subproject: it only runs it for root project. That's why I add

ktlintCheckAll

:

tasks.register("ktlintCheckAll").configure {
    rootProject.subprojects.flatMap {
  it.tasks.withType(BaseKtLintCheckTask).matching { t -> t.name == "ktlintCheck" }
}

}

thus,

root build.gradle

tasks.register("staticAnalysis") {
    dependsOn(tasks.named("ktlintCheckAll"))
}

to enforce running all

ktlintCheck

for all subprojects

you need all sub projects

ktLintCheck

task depends on a

staticAnalysis

task registered in each sub project

makes sense but still - what if I want a "root" task. How to do so? Am I right?

yeah

ok, how to express the intention that I would like to run a task w/o indicating a module, in build.gradle script?

I don't understand what you mean

how to express

./gradlew ktlintCheck

instead of

./gradlew :ktlintCheck

in gradle scripts?

I think you are mixing things

that means I cannot use "first" in build scripts

Exactly. Well, you need

subprojects

to do it, but usually this should simply not necessary. Why do you want to have a root task that depends on all subproject tasks? Just when you invoke, invoke the right one.