Hi I was wondering how can I generate the `symbol processing kotlinlang #ksp

artifact locally? I see it's only created to be published in Maven (https://github.com/google/ksp/pull/541), but I don't see a way to generate it myself in case I want to test the 1.5.30 branch for example. It's also unclear to me what is the difference between that and the regular

symbol-processing

artifact. I know the cmdline variant is necessary for Kotlin Native and command line, but why is that?

Ting-Yuan Huang

08/23/2021, 10:29 PM

If you're using it locally, it's available as

compiler-plugin/build/libs/compiler-plugin-<version>.jar

after build. Publishing to maven local (e.g.,

./gradlew publishToMavenLocal

) also works, with the jar renamed to

symbol-processing-cmdline-*.jar

symbol-processing

and

symbol-processing-cmdline

are built with

kotlin-compiler-embeddable

and

kotlin-compiler

respectively. The difference is that some intellij dependencies are renamed and bundled in

kotlin-compiler-embeddable

, which is a fat jar. Because some of the intellij symbols are used in compiler plugin interfaces, compiler plugins (e.g., KSP) need to have different builds for them as well.

Udi Cohen

08/23/2021, 10:53 PM

OK thanks for clarifying. So the generated compiler-plugin-<version>.jar is the same jar we get with the

symbol-processing-cmdline

artifact, and the

symbol-processing

artifact is constructed a bit differently to embed the compiler and other stuff. Is that right? If I want to fix stuff in the

symbol-processing-cmdline

artifact, I can just directly use the compiler-plugin-<version>.jar for my tests?

Ting-Yuan Huang

08/23/2021, 11:00 PM

yes, that's right

2 Views

#ksp Join Slack