I am registering a task and it is automatically run when the IDE syncs. Every single time I press th...

# gradle

[Javier]

I am registering a task and it is automatically run when the IDE syncs. Every single time I press the sync button. When I run gradlew build, it doesn't run. I tried both, register and create, same problem. Is it a bug or is it the expected behavior?

[mbonnin]

The IDE Sync is not invoking a Gradle task directly, it's using the Gradle tooling API to inspect the build. There's no direct link between "Sync" and "build" (or tasks in general FWIW)

[mbonnin]

I'd love to have a Gradle plugin that creates a task that emulates what IntelliJ is doing but that seems very unlikely to happen

[Javier]

The task is changing files, and then when I sync the project, the files are changing too. It is a real problem

[Javier]

I am going to check if there is an open issue about this

[mbonnin]

I get the impression that "Sync" sometimes calls "javaGenerating" tasks

[mbonnin]

(or maybe kapt)

[mbonnin]

But haven't really found a pattern there

[Javier]

https://youtrack.jetbrains.com/issue/IDEA-272518

[tapchicoma]

as far as I know sync triggers all tasks creation, but not action execution

[tapchicoma]

@Javier it will help if you could provide project to reproduce the issue

[Javier]

Mmm okay, basically I am publishing a precompiled plugin to maven central which is registering a task, and adding it to another project

[Javier]

I will add them later

[Vampire]

You most likely do something wrong, like doing work in the configuration phase instead of execution phase or similar. But without you providing an MCVE here or in that issue, all is guesswork. And even if it were a bug, it would not be fixable without an MCVE.

[Javier]

it is a precompiled plugin applied to the root project which is registering a task which just use file().writeText(...)

[Javier]

https://github.com/JavierSegoviaCordoba/gradle-plugins/blob/main/buildSrc/src/main/kotlin/plugins/massive-catalogs-updater.gradle.kts

[Javier]

https://github.com/JavierSegoviaCordoba/gradle-plugins/blob/main/build.gradle.kts

[Vampire]

Yep, exactly what I suspected and said.

[Vampire]

You are doing the work at configuration time.

[Vampire]

So every time your task is configured your logic is done

[Vampire]

You miss a doFirst or doLast

[Javier]

ah okay

[Javier]

thank you 🙂

[Javier]

I didnt know I have to write to the file in doLast

[Vampire]

Whatever you do outside of doLast or doFirst is done during configuration phase, every time your task is configured, whether it will be executed or not.

[Vampire]

https://docs.gradle.org/current/userguide/userguide_single.html#sec:build_phases

[Javier]

@tapchicoma is it possible to I can close the issue in youtrack

[tapchicoma]

please close

[Vampire]

You cannot close as user, can you?

[Vampire]

I never was able yet

[Vampire]

Always had to let JB people do it

[Javier]

I can't, or I can't see how

[Javier]

If DefaultTask is used, it is necessary using doFirst and doLast too, no?

[Vampire]

Everything in the @TaskAction method is in execution phase already

[Vampire]

doFirst and doLast are only for ad-hoc tasks or to add actions to existing tasks

[Javier]

TIL, thank you 🙂