KT-24486 - Opening a .gradle.kts file in an imported Gradle project pollutes the package list with empty packages

[big-guy]

When I import kotlin-dsl, I see a reasonable list of packages, but as soon as I open a .gradle.kts file, the list of packages in each module explodes to include the Gradle API packages. Closing/opening the project doesn't clear the list.

This happens in gradle/gradle's buildSrc project too. I've seen this happen in standalone plugin projects too.

Steps to Reproduce (for bugs)

I had commit 6dd79ff checked out. I ran git clean -fxd to make sure there wasn't any Intellij files laying around.

After importing kotlin-dsl, I see this list of packages in the plugins project:

After opening provider/build.gradle.kts:

This appears to be the shaded Gradle API jar packages. I'm not sure if this is something we're feeding to IntelliJ or a bug on IntelliJ's side?

Your Environment

macOS, IntelliJ 2018.1

[eskatos]

Never seen this before 👀

Ah, it isn't in the Project view but in the Packages view.
Here with one module per source set, but the issue is the same:

Looks like somehow IntelliJ puts the packages of the script dependencies, empty, in that context.
Good catch @big-guy!

[eskatos]

Issue opened upstream at https://youtrack.jetbrains.com/issue/KT-24486

[bamboo]

Those are probably there because we serve the shaded gradleApi() jar to the IDE. Maybe we should serve the actual jars from the distribution instead?

[eskatos]

There are packages not coming from gradleApi() in the ones that show up in the Packages view.