what is the correct way to always run another task after a b kotlinlang #gradle

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

janvladimirmostert

07/10/2020, 8:13 PM

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

07/10/2020, 8:13 PM

you want to get the task build,

tasks.get("build")

tasks["build"]

janvladimirmostert

07/10/2020, 8:14 PM

awesome, thanks Octavia!

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

07/10/2020, 8:17 PM

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

build

task

janvladimirmostert

07/10/2020, 8:18 PM

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

gradle build

octylFractal

07/10/2020, 8:18 PM

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

gradle build

refers to all tasks named

build

, not a task in the root project named

build

gradle :build

is specifically the

build

task in the root project

janvladimirmostert

07/10/2020, 8:21 PM

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

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

07/10/2020, 8:34 PM

I would be surprised if dependsOn is circular?

it means that

jsPublicPackageJson

dependsOn

build

for some reason, which should really not be the case

janvladimirmostert

07/10/2020, 8:36 PM

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

araqnid

07/10/2020, 10:09 PM

you can also write

subprojects{}

in the root instead of

allprojects{}

if that suits better

janvladimirmostert

07/10/2020, 10:14 PM

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

gildor

07/11/2020, 5:09 PM

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

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

👍 2

4 Views

#gradle Join Slack