Is there a way to rollback to the Kotlin 1.8.21 plugin for IJ 2023.1? I just tried reinstalling IJ 2...

# intellij

[edwinRNDR]

Is there a way to rollback to the Kotlin 1.8.21 plugin for IJ 2023.1? I just tried reinstalling IJ 2023.1 from toolbox but that automatically installs the 231-1.9.0 plugin

[edwinRNDR]

https://plugins.jetbrains.com/plugin/6954-kotlin/versions/stable doesn't list a 1.8.21 plugin for 231, the 223 version is not compatible (I tried installing it anyway)

[edwinRNDR]

Reason for wanting to downgrade is a showstopper bug in 231-1.9.0 that causes secondary sourcesets to be marked as test roots. This happens only on Windows for me, it works fine on Linux using the same plugin and IJ builds.

[edwinRNDR]

re-installing IJ by downloading it from the website works btw.

[Anton Mefodichev]

You can try the following: open Settings - Plugins - Kotlin plugin, then Uninstall it. Check the plugin version after IDE restart.

[edwinRNDR]

I will give this a shot

[edwinRNDR]

I'm also looking for some help reporting this bug (or identifying an existing report). Where do I report it? Do I need to make a MVP?

[Anton Mefodichev]

You can report the bug directly to YouTrack:
https://youtrack.jetbrains.com/newIssue
In general if you attach simple project with the issue reproduction, it really helps for the issue investigation. Thank you!

[Abe Sol]

I'm having the same error on Manjaro Linux. It seems to believe it's a Python test? But this is a Kotlin/Gradle project and the folder does not contain tests.

[Abe Sol]

Uninstalling the 1.9.0 plugin solved it for me. With plugin 1.8.21 I can run the demo programs in that project again.

[Abe Sol]

The steps to reproduce the issue for me were
• Use Idea Community edition with Kotlin plugin 1.9.0
• Clone and open orx in Idea
• Open one of the demo programs, for instance orx/orx-color/src/jvmDemo/kotlin/DemoColorRange01.kt
• The folder containing that .kt file is green and marked as containing tests
• Try to run the program by right clicking on it. It fails to run.
• Moving back to plugin 1.8.22 solves the issue.

[Anton Mefodichev]

@Abe Sol, thank you!
https://youtrack.jetbrains.com/issue/KTIJ-26469

[edwinRNDR]

Thanks @Anton Mefodichev

[Abe Sol]

Workaround: enable the fallback flag in gradle.properties for the old IDE behavior:

kotlin.mpp.import.legacyTestSourceSetDetection=true

[Abe Sol]

(suggested in youtrack)