This message was deleted.
# community-supports
Slackbot
10/18/2023, 8:20 PMThis message was deleted.
c
Chris
10/19/2023, 12:51 PMOkay… I think I’m falling victim to https://youtrack.jetbrains.com/issue/KTIJ-25989, or perhaps some other fallout from https://youtrack.jetbrains.com/issue/KTIJ-25910. I’d suggest most people avoid upgrading to 2023.2.x to avoid any issues with Kotlin based Gradle builds. It’s reportedly fixed in the EA of 2023.3… so I guess thats another option, but I went back to 2023.1.5 instead.
Chris
10/19/2023, 12:53 PMI guess this does make me wonder what testing the Gradle team do on IntelliJ EA releases, and whether the IntelliJ team would consider a Gradle issue a showstopper? Given how tightly Gradle has tied itself to Kotlin and therefore the IntelliJ ecosystem, I’d hope the answers are: “lots” and “yes”.
v
Vampire
10/19/2023, 1:35 PMI'd say that kind of testing should be done on IntelliJ side, and as Gradle is very popular also hope for a "yes" to the second question. 🙂
It is most probably out of scope of Gradle testing to test against IntelliJ versions.
c
Chris Lee
10/19/2023, 1:47 PMI’d suggest most people avoid upgrading to 2023.2.x to avoid any issues with Kotlin based Gradle builds.fwiw on 2023.2.x, have many Gradle/Kotlin DSL projects and have not run into this issue.
c
Chris
10/19/2023, 1:48 PMsorry… it’s clearly not “everyone”… and the IntelliJ issues were vague on what the triggering condition was
Chris
10/19/2023, 1:49 PMsimplest solution for me was to downgrade and move on… especially since IntelliJ are aware of the issue
👍 1
4 Views