This message was deleted.

You are explicitly specifying to run the

clean

task of the root project of the included build. That is the same as if you would say

./gradlew :clean

in the included build. There is as far as I know no way yet to do the magic "run the task in all projects that have it if any" that you probably intend. You can for example make a

clean

task in the root project of that included build that fans out to all the subprojects, or you could make a task in your including build that fans out to the subprojects of the included build.

link to do the fan out?

Setting up the according dependencies is what I meant, there is no automatic fan-out except for the command-line special handling of tasks without a given project-path.

hmm bummer. okay i'll log a feature request

Link it here so people can find it 🙂

k thanks

I think I'd rather just move to the included build and run

./gradlew clean

(adjusting path for

gradlew

as needed if you don't have one there), or even simpler:

./gradlew -p path-to-the-included-build clean

.

i did the first suggestion but ran into an issue with gradle cache. I have not tried the

-p

argument, i'll try that!