Navigating to Gradle plugin source in debugger

There is indeed an issue with the source resolving of the kotlin libraries in the context of the gradle build script (Groovy DSL). I'm afraid there is no simple workarounds right now, please file an issue request for the support. Thanks!

Thanks. Does this issue only occur for the Kotlin plugin, or does it occur for all plugins?

If I understand you correctly, only kotlin sources (*.kt files) can not be resolved for gradle groovy build scripts. So, it affects gradle plugins written in kotlin and other plugins if it has kotlin libraries dependencies.

I don’t know if the source for the classes to which I can’t navigate is Kotlin or Java (or any other JVM language, for that matter). All I know is that the ByteCode is part of the Kotlin plugin for Gradle. Are you just guessing that IntelliJ fails to load `.kt`, and only `.kt`, files from any Gradle plugin’s source, or have you actually done tests, or seen others’ tests, that confirm that is causing the symptoms I see? I just want to make my bug report accurate, so I don’t waste JetBrains dev’s time with potentially erroneous diagnoses of root causes of the symptoms I’ve seen.

There were some complains about kotlin classes usage inside gradle build scripts. I've filled the issue request at https://youtrack.jetbrains.com/issue/IDEA-196892 . Feel free to attach the simple project sample to illustrate the issue you've seen.

I’m actually using the Gradle Kotlin DSL, not the Groovy DSL. I much prefer static languages over dynamic ones.

Then it's a different issue, please file a separate ticket with the sample project attached.

I filed a broader request for debugging to support navigating to the source of plugins from the Gradle Plugin Portal, since this doesn't seem to be limited to the Kotlin plugin:

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