what is the correct way to always run another task after a build? I've tried ```task("build").finali...

# gradle

[janvladimirmostert]

what is the correct way to always run another task after a build?
I've tried

task("build").finalizedBy("jsPublicPackageJson")

but it complains Cannot add task 'build' as a task with that name already exists.

[octylFractal]

you want to get the task build, tasks.get("build") or tasks["build"]

[janvladimirmostert]

awesome, thanks Octavia!

[janvladimirmostert]

Task with name 'build' not found in root project '....'.

This is for my root build.gradle.kts file, does it not have a build task?

adding it under allprojects { } is giving he same message

gradle.buildFinished works, so it must have a build task

[octylFractal]

I'm not sure what your logic is for that last line -- a build != running the build task

[janvladimirmostert]

ok, does the root build.gradle.kts make use of a different task when you do gradle build ?

[octylFractal]

build is just a convenient way to run assemble and then check, it is added by the lifecycle plugin, so if you don't have any plugins applied to the root, it doesn't exist

[octylFractal]

gradle build refers to all tasks named build, not a task in the root project named build

[octylFractal]

gradle :build is specifically the build task in the root project

[janvladimirmostert]

i'm coming from the maven world where the lifecycles are fixed, it's taking a bit of getting used to

[janvladimirmostert]

got it running by moving this into the sub project's build.gradle.kts

dependsOn seems to create a circular dependnecy, so used mustRunAfter

tasks.get("build").mustRunAfter("jsPublicPackageJson")

thanks for the help, it's much appreciated!

[octylFractal]

I would be surprised if dependsOn is circular?

[octylFractal]

it means that jsPublicPackageJson dependsOn build for some reason, which should really not be the case

[janvladimirmostert]

correction, finalizedBy was causing the circular dependency, dependsOn works as you said

[araqnid]

you can also write subprojects{} in the root instead of allprojects{} if that suits better

[janvladimirmostert]

i should try that, allprojects includes the root project which i usually don't want when i'm looping through subprojects

[gildor]

Do not use tasks.get(“build”), it forces task to be configured eagerly, use configuration block:

tasks.named("build") {
   mustRunAfter("jsPublicPackageJson")
}