A modern programming language that makes developers happier.

kotlinlang

```tasks.register("clean", Delete::class) {
    delete(rootProject.buildDir)
}```
this is the default clean task. Does this need to look different for multi-module projects or will this work just fine?

maybe `delete(rootProject.buildDir)` needs to be run on each buildDir? im not sure though

In multi module project every module should have own clean task

How would I run all those tasks simultaneously

and this task implementation doesn’t look right, every module has build dir, not only rootProject

why do you need custom clean task at all?

for the same reason you would need any clean task. I want to clear out any generated code

but default clean task already doing this

if you need something custom (to delete some dir outside of `build` dirrectory, you just add your custom task as dependency to default `clean` task

at least it was in the project build file when the project was created

It’s not “default” it’s just generated by some project generator

see, every module with base plugin has clean task:
<https://docs.gradle.org/current/userguide/base_plugin.html>

except root module, which doesn’t apply any plugins (at least in default android project), so this task is just delete root build dir, but it really not important, you just can delete it

all modules where you really need clean, already have clean task

this custom task just deletes root build dir

ohh ok that makes sense. I didnt know that there was a default clean task already

Yes, and returning to your question
&gt;  How would I run all those tasks simultaneously
This how Gradle works by default with all the tasks, if you do  this: `./gradlew clean` . Gradle will check every module, if it has task clean and run it, if it doesn’t, nothing happen

If you do this: `./gradlew :some-module:clean` it will run clean task only on some-module, or `./gradlew :clean` it will run clean task only on root module

ah ok. I think I need to learn more about gradle...