Task configuration avoidance is defeated by IDEA import/sync

[ldaley]

When importing/syncing a build in IDEA. all tasks are realized. This means that if one is using the configuration avoidance constructs to avoid expensive configuration (e.g. IO) unless the task is needed, this slows down the IDE sync. This reduces the “reliability” of configuration avoidance for avoiding expensive configuration.

Ideally, IDE sync wouldn't need to realise all of the tasks and the existing constructs would just work. Failing that, more targeted constructs may be necessary, or falling back to existing informal constructs such as configuration tasks or taskGraph.whenReady deferrals.

[oehme]

I think this is more of an issue on the idea side. Idea needs all tasks to populate the tasks view, including groups and descriptions. However this is not needed for the basic function of editing your project. So it could fetch the information for the tasks view later.

[big-guy]

It's on both sides. To build the GradleProject model, we realize all the tasks and there's not a way to say you don't need that information and GradleProject is attached to all of the IDE models. We could maybe replace this with a "lite" GradleProject

[oehme]

I see, we should deprecate that and only leave ProjectIdentifier in place.

[technoir42]

I stumbled upon this issue after migrating all the plugins in our project to support configuration avoidance. Was that work all for naught? The performance of IDE sync was the main reason we invested in moving to the new task APIs.

The problem can be easily reproduced by adding a task like this to any project:

tasks.register("unusedTask") {
    throw new GradleException("Should not be configured")
}

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[technoir42]

Still relevant.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[abbas-gadhia]

The problem mentioned by @technoir42 still exists in Intellij 2021.2.1
We wanted to improve our IDE sync times but looks like this issue is a blocker for that

[leni8ec]

I also experienced this problem - are there any plans to fix it? If it is a problem on the Intellij IDEA side, where can I report it?

Task configuration avoidance by tasks.register() is ignored on 'Gradle Reload' event in Intellij IDEA (or Android Studio)

It's also confusing that right before this, the task: prepareKotlinBuildScriptModel is called - because I thought that it was the cause. But it has no relation to this, you can check this - by disabling the 'Kotlin' plugin in IntellijIDEA

Mention of this problem: link

[nikitasius]

annoying kotlin shit in my java project

[xtracoder]

Not sure, maybe disabling "Kotlin" plugin in IDEA will help

[daymxn]

+1

We're having this issue over at Google as well.

[gleb-skobinsky]

Same issue, still relevant in Intellij 2023.2.1