Why were these made `internal` in 1.9.0? Is there ...

# eap

[Zac Sweers]

Why were these made internal in 1.9.0? Is there a different API that should be used for compiler plugins?

e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:23:43: Cannot access 'NATIVE_COMPILER_PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:24:43: Cannot access 'PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:179:13: Cannot access 'PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'
e: file:///Users/zacsweers/dev/slack/oss/circuit/build.gradle.kts:180:13: Cannot access 'NATIVE_COMPILER_PLUGIN_CLASSPATH_CONFIGURATION_NAME': it is internal in 'org.jetbrains.kotlin.gradle.plugin'

[tapchicoma]

please open an issue with your use-case

[Zac Sweers]

https://youtrack.jetbrains.com/issue/KT-58916

[Zac Sweers]

It seems that these are no longer the configurations used either, as I’m seeing in our project (https://github.com/slackhq/circuit/pull/643) that adding add("kotlinNativeCompilerPluginClasspath", libs.androidx.compose.compiler) to compose multiplatform projects is not resulting in the newer compose compiler actually being used. Is there a new configuration name these should be added to for KotlinNativeCompile? CC @Sebastian Sellmair [JB]

> Task :backstack:compileKotlinIosSimulatorArm64 FAILED
e: This version (1.4.5) of the Compose Compiler requires Kotlin version 1.8.20 but you appear to be using Kotlin version 1.9.0-Beta which is not known to be compatible.  Please consult the Compose-Kotlin compatibility map located at <https://developer.android.com/jetpack/androidx/releases/compose-kotlin> to choose a compatible version pair (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

[Sebastian Sellmair [JB]]

Thanks the cc! Zac, am I right, that you basically want an API where you can ‘universally’ add compiler plugin dependencies?

[Zac Sweers]

Yep, but also curious in the meantime if the configuration used for native compilations changed in 1.9.0

[Zac Sweers]

@Sebastian Sellmair [JB] filed this one for the above https://youtrack.jetbrains.com/issue/KT-59085

[Sebastian Sellmair [JB]]

Will take a look at the whole situation next week! Thank you 😎