Hi everyone, Wanted to share an update on KSP and...

# ksp

[Ting-Yuan Huang]

Hi everyone,

Wanted to share an update on KSP and our development process.

After discussing with the Kotlin compiler maintainers, we’ve decided to move KSP to its own repository on GitHub and decouple it from the compiler project. The Kotlin compiler teams at JetBrains and Google remain very committed to this project and making it a core part of the Kotlin toolchain. But, as the Kotlin compiler codebase grows in size and complexity, we’ve decided it makes more sense to decouple KSP to keep our development and releasing processes fast and efficient.

That said, we will continue to rebase onto new versions of the Kotlin compiler and, in fact, you can check out our latest Kotlin 1.4.10-compatible release here. As always, we’re open to your feedback and suggestions — please don’t hesitate to reach out if you have any questions about this decision or anything else on KSP.

Along with the repository change, we’ve also changed the package name as well. Here is an example of how to make your project use the new KSP release.

[evant]

The README has

when (requested.id.id) {
                "symbol-processing" ->
                    useModule("com.google.devtools.ksp:symbol-processing:${requested.version}")
            }

and then

id("kotlin-ksp") version "1.4.10-dev-experimental-20200924"

that won't resolve right? the second line should be

id("symbol-processing") version "1.4.10-dev-experimental-20200924"

right?

[Ting-Yuan Huang]

You're right. Thanks for noticing that. Will update asap

[Jan Skrasek]

Does it mean that it won't be an official JetBrains' toolchain for Kotlin? Or do you plan switch package name again?

[Ting-Yuan Huang]

We'll switch package name again if upstreaming is necessary.