Then another question. Why do the docs recommend to do continuous build on the `build` task, while t...

# ktor

[Arjan van Wieringen]

Then another question. Why do the docs recommend to do continuous build on the build task, while the classes task is much faster, because it does not generate all the following:

> Task :checkKotlinGradlePluginConfigurationErrors
> Task :compileKotlin UP-TO-DATE
> Task :compileJava NO-SOURCE
> Task :processResources UP-TO-DATE
> Task :classes UP-TO-DATE
> Task :jar
> Task :startScripts
> Task :distTar
> Task :distZip
> Task :shadowJar
> Task :startShadowScripts
> Task :shadowDistTar
> Task :shadowDistZip
> Task :assemble
> Task :compileTestKotlin UP-TO-DATE
> Task :compileTestJava NO-SOURCE
> Task :processTestResources NO-SOURCE
> Task :testClasses UP-TO-DATE
> Task :test
> Task :check
> Task :build

And classes does this:

> Task :checkKotlinGradlePluginConfigurationErrors
> Task :processResources UP-TO-DATE
> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :classes UP-TO-DATE

[jw]

build runs assemble and check. The former does everything required to produce the final binary. The latter does everything required to validate the behavior is correct.

[Arjan van Wieringen]

But for auto reload behavior it would make sense to only run classes. Unless you’re interested in continuous tests