my build has some "discoverMainScriptsExtensions" ...

# announcements

[pniederw]

my build has some "discoverMainScriptsExtensions" tasks (presumably added by Kotlin plugin) that are never UP-TO-DATE. what are those, and how can I get rid of them?

[Alexey Belkov [JB]]

This is fixed in 1.3.20 https://youtrack.jetbrains.com/issue/KT-28469

[pniederw]

@Alexey Belkov [JB] can these configuration tasks be made opt-in? I suspect most users won't ever need them because they don't use kotlin scripting (which is what I suppose this is about).

[pniederw]

50 additional tasks in my build (25 subprojects * 2) is a lot of unnecessary noise.

[Alexey Belkov [JB]]

Have you tried 1.3.20 EAP https://discuss.kotlinlang.org/t/kotlin-1-3-20-early-access-preview/10748 ? Is it still a problem there?

[pniederw]

I haven't tried it, but the issue suggests you fixed the up-to-date check, which means that in the best case, I'll still get 50 times "discoverXYZ UP-TO-DATE" cli output every time I run my build, even though I'm not using Kotlin scripting at all.

[pniederw]

Until I searched the Kotlin plugin source code, I had no idea where these tasks were coming from and what they were doing. It's pure noise from my perspective.

[pniederw]

Configuration tasks are a common workaround when using third-party legacy tasks, but I think the Kotlin plugin should be able to do better.

[pniederw]

e.g., I'm not aware of any use of configuration tasks in Gradle's own plugins.

[Alexey Belkov [JB]]

Ok, I just check it, on 1.3.20 EAP there is no mention of this task with command ./gradlew clean build -i. Seems like it shouldn't be a problem. If it is, please file a new issue at http://kotl.in/issue. Thanks!

[pniederw]

sounds like you did eliminate them after all. I'll give it a try. thanks!