You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This slows down builds because it forces tasks to be created and configured, even if they won’t be executed by the current Gradle execution.
Unfortunately I think this might be a bit tricky. I don’t see an obvious way to get another plugins’ task names without also causing those tasks to be configured. And we need these names, cause our names are built on their names. (It’s possible we can do something like tasks.withType.names and track when that set changes?)
The text was updated successfully, but these errors were encountered:
We’re causing all
KotlinWebpack
andKotlinCompile
tasks to be created eagerly because we’re using APIs like this:This slows down builds because it forces tasks to be created and configured, even if they won’t be executed by the current Gradle execution.
Unfortunately I think this might be a bit tricky. I don’t see an obvious way to get another plugins’ task names without also causing those tasks to be configured. And we need these names, cause our names are built on their names. (It’s possible we can do something like
tasks.withType.names
and track when that set changes?)The text was updated successfully, but these errors were encountered: