Update 2.1.0 internal compiler APIs doc #4631
Conversation
| @@ -1249,16 +1249,21 @@ You can use the `KotlinAndroidExtension` in exactly the same way. | |||
|
|
|||
| ### Compiler symbols hidden from the Kotlin Gradle plugin API | |||
|
|
|||
| Starting with Kotlin 2.1.0, | |||
| you will receive a warning if you access compiler module symbols bundled within the Kotlin Gradle plugin (KGP). | |||
There was a problem hiding this comment.
I think this was technically not exact, right? The warning is based on the presence of a class file that is not bundled in KGP but build logic could still use the symbols bundled with KGP without being detected?
docs/topics/whatsnew21.md
Outdated
|
|
||
| To guard against those issues, KGP will now display a warning if `org.jetbrains.kotlin:kotlin-compiler-embeddable` is loaded in the build classpath alongside KGP. | ||
|
|
||
| As a long term fix, if you are a plugin author using `org.jetbrains.kotlin:kotlin-compiler-embeddable` classes, we recommend doing so in an isolated classloader. |
There was a problem hiding this comment.
Changed from a requirement to a recommendation. If KGP removes any dependency on compiler APIs and/or the compiler APIs become stable, it might become acceptable to do the work in the main build classpath?
Also Gradle Workers API is a possible solution but it comes with tradeoffs so it's leaving the door open to other solutions.
There was a problem hiding this comment.
It might become acceptable but is still subject to conflicts between different plugins that depend on kotlin-compiler-embeddable. The artifact does not provide generic compatibility guarantees as it's a fat jar containing both public and internal APIs.
apply Kotlin documentation styleguide
delete unnecessary new lines
|
Works for me! Thanks for the follow up! |
Follow up from this slack thread: https://kotlinlang.slack.com/archives/C19FD9681/p1735830883666549