I need to run a copy task everytime the task kspKotlin successfully passes, I have the following cod...

# gradle

[Charlie Tapping]

I need to run a copy task everytime the task kspKotlin successfully passes, I have the following code which seems to work okay:

afterEvaluate {
    tasks.named("kspKotlin") {
        finalizedBy(copyFeatures)
    }
}

I read somewhere whilst learning that finalizedBy happens irrespective of kspKotlin being successful or not, is there an alternative that works only on success? Also is there anyway to avoid the afterEvaluate because I can’t seem to find that task without that block?

[Adam S]

what you might want is instead to hook into a ‘lifecycle task’

https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:lifecycle_tasks

so instead of making kspKotlin be finaized by copyFeatures, instead

1. make copyFeatures { dependOn(tasks.kspKotlin) }
2. make a lifecycle task, like assemble, depend on copyFeatures
That way every time assemble runs, it will run kspKotlin and copyFeatures in the right order.

But… what does copyFeatures do? Does it copy generated source code into a src dir?

[Charlie Tapping]

Copy features is essentially this:

val copyFeatures by tasks.registering(Copy::class) {
    from(file("$rootDir/xxx/build/generated/ksp/main/resources/features-gen.yml"))
    rename { "features.yml" }
    into(file("$rootDir/.xxx/"))
}

[Charlie Tapping]

One of my KSP outputs is a yaml file

[Adam S]

Yeah okay, that makes sense. What happens to the yaml file get used for afterwards? Are there any other tasks that require it exists? I ask because it’s possible to convert the copyFeatures task into a ‘file provider’ and use it as a srcDir in a source set, or something, and that makes sorting out task ordering easier

[Charlie Tapping]

The yaml file is actually picked up by a process in CI, its entirely unrelated to anything else

[Adam S]

gotcha

[Charlie Tapping]

So this is okay?

tasks.named(LifecycleBasePlugin.BUILD_TASK_NAME) {
    dependsOn(copyFeatures)
}

[Charlie Tapping]

I actually need it to run on build as opposed to assemble

[Adam S]

yes that makes sense 👍

[Charlie Tapping]

Thank you Adam !

[Adam S]

you’re welcome!

[Vampire]

You can also have kspKotlin finalized by copyFeatures and copyFeatures dependsOn kspKotlin.
Then it is always run after successful kspKotlin execution if that really is what you want.

[Charlie Tapping]

Oddly the lifecycle task block never seems to trigger the copyFeatures task

[Charlie Tapping]

I tried assemble also

[Charlie Tapping]

neither seem to be triggered when building my android application

[Vampire]

Run with -m and you will see which tasks would get executed.

[Charlie Tapping]

Yeah the copy task doesnt ever seem to get registered, I must be doing something silly

[Charlie Tapping]

The finalized approach I posted originally works but I was trying to avoid the after evaluate

[Vampire]

Then find out why the task is not present already.
Is the plugin not yet registered?
Does it itself use afterEvaluate to register the task?
...?
Many possibilites.

[Vampire]

Worst case:

tasks.configureEach {
    if (name == "kspKotlin") {
        finalizedBy(copyFeatures)
    }
}

[Charlie Tapping]

I wonder if its because my android application has variants, so assemble is in fact assembleStaging? Technically they’re different tasks?

[Vampire]

Of course they are different tasks. But I cannot reason about Android, I don't do Android development.