You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kotlinx.coroutines library is about to change the name of the kotlinx.coroutines.debug.AgentPremain class, which we refer to with the dynamically created coroutines-javaagent.jar file, required for coroutines debugging to work:
As soon as the Kotlin/kotlinx.coroutines#4247 change is applied and introduced to the IntelliJ Platform, we need to adjust that name in the IntelliJ Platform Gradle Plugin, too.
For backward compatibility, we need to keep the reference to the old class in place and introduce a new one with the IntelliJ Platform build number check.
A new file has to have a new name to allow the use of IntelliJ Platform in an older version next to the newer platform version, i.e., when one builds the plugin with a different version than when running it locally.
In some cases, it may also be necessary to manually allow plugin developers to switch to the new approach by enabling the dedicated feature flag.
The text was updated successfully, but these errors were encountered:
The
kotlinx.coroutines
library is about to change the name of thekotlinx.coroutines.debug.AgentPremain
class, which we refer to with the dynamically createdcoroutines-javaagent.jar
file, required for coroutines debugging to work:intellij-platform-gradle-plugin/src/main/kotlin/org/jetbrains/intellij/platform/gradle/tasks/InitializeIntelliJPlatformPluginTask.kt
Lines 145 to 153 in b9b6699
As soon as the Kotlin/kotlinx.coroutines#4247 change is applied and introduced to the IntelliJ Platform, we need to adjust that name in the IntelliJ Platform Gradle Plugin, too.
For backward compatibility, we need to keep the reference to the old class in place and introduce a new one with the IntelliJ Platform build number check.
A new file has to have a new name to allow the use of IntelliJ Platform in an older version next to the newer platform version, i.e., when one builds the plugin with a different version than when running it locally.
In some cases, it may also be necessary to manually allow plugin developers to switch to the new approach by enabling the dedicated feature flag.
The text was updated successfully, but these errors were encountered: