I’m attempting to use

blockOtherCompilerPlugins

but I’m not sure I quite understand its intended use. I’m trying to disable Anvil from running during KSP’s tasks, but when I set this property to true I get an obscure NoSuchElementException coming from this line: https://github.com/google/ksp/pull/270/files#diff-a345032d6c965be6e81478437767cb750c83bd0a952014661e86d454ea5a342bR223 Is this the right way to use this?

@Ting-Yuan Huang Are we still going to see KSP enabled for multiplatform in Kotlin 1.5.20? 1.5.10 was just released, so I thought I’d check in 🙂

Hey everyone, we’re excited to announce the first beta release of KSP! Big thanks to everyone in this group for all of the helpful feedback over the last 3 months. The existing API should be mostly stable now and unlikely to change in the future. We'll do our best to minimize the compatibility / migration issues from now on. As for next steps, we'll be focusing on fixing bugs, tuning performance and multiplatform support. Please give it a try and let use know what's needed and what doesn't work!

for

KSNode.origin

I see Origin can be both

KOTLIN

or

KOTLIN_LIB

. Do both of those indicate that the node is a kotlin type? I'm curious what the distinction implies

Not sure if this is best to post in #room or here, I upgraded to Compose beta08 today, which allowed me to jump to 1.5.10-1.0.0-beta01 of KSP. Since doing this (only version changes) KSP has stopped generating anything. I've tried Room 2.4.0-alpha02 and 2.3.0. Were there any Gradle configuration changes required for the jump from 1.4.32-1.0.0-alpha08 -> 1.5.10-1.0.0-beta01? Everything works fine if I switch back to kapt.

We have a pretty basic preprocessor task coming (generating a documentation file containing all the classes/methods in the project with a special annotation). Normally I'd use KAPT, since KSP is still in Alpha, but it's unclear if KAPT will support the new compiler frontend. So how is the situation with KSP? Does it already work with the new frontend? Since my task is so straight forward, I think, I'd be ok with updating/adapting my code through different alpha versions of KSP, or is this a bad idea?

Is it possible to retrieve all classes/interfaces implementing a particular interface with ksp?

Any suggestions on a test case for my PR fixing bytecode post processing?

Super basic question, how do y'all google questions around ksp? 🙈 Every time I try to google something ksp-related I only get things about Kerbal Space Program 😂

What's the state on ksp on multiplatform? According to some issues and merged PR's it seems that it might be supported, but the readme states that it's still on the roadmap.

hm, will try to narrow it down more sometime later, but getting an error type somewhere just on js, can reproduce by running

./gradlew jsTest

from the

ksp-js

branch https://github.com/evant/kotlin-inject/tree/ksp-js

The alpha release blog post says

using KAPT and KSP in the same module will likely slow down your build initially

- however, we did some gradle profiling of our own project with KSP enabled and found that mixing KSP/KAPT actually is slightly faster than using only KAPT (if not all processors support KSP) I’m wondering if there is any more current information about mixing KAPT and KSP in the same module (since alpha release was a while ago), and I’m curious to hear about other people’s experience

I wrote some code to implement the

getAnnotation

in a separate repo. I saw that the implementation is pending for KSP and would like to know if I could help contribute there. If so I have a couple of questions. Which elements should we apply the functions to? I was thinking the KSAnnotated seems to make sense. ie

KSAnnotated#getAnnotation

I had also thought of taking a different approach and leveraging the

Method#getAnnotation

method by just getting a handle to the

Method

itself from the

KSAnnotated

, but I hadn’t done any further research into that yet. What approaches were you thinking about taking? And does my current implementation in my repo seem reasonable or is there a better approach? I had thought about just creating a PR, but I would rather get some feedback first before I invest the time. Thanks

Hi! I have a question: why KSNameImpl doesn't override equals method? Wouldn't it be easier to write this

it.simpleName == shortName

instead of this

it.simpleName.asString() == shortName.asString()

. Before looking into the impl, I even thought that calling

asString()

is not efficient, because conversion from some inner representation to String might happen.

Running the following command

./gradlew --stacktrace --info :compiler-plugin:test --tests "com.google.devtools.ksp.test.KotlinKSPTestGenerated.*" -PcompilerTestEnabled=true

any idea how to fix the error below when I attempt to run the tests locally. Every test fails with the same error.

com.google.devtools.ksp.test.KotlinKSPTestGenerated > testAnnotationOnConstructorParameter FAILED
    java.lang.NoClassDefFoundError: Could not initialize class sun.lwawt.macosx.LWCToolkit
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:292)
        at java.desktop/java.awt.Toolkit$2.run(Toolkit.java:573)
        at java.desktop/java.awt.Toolkit$2.run(Toolkit.java:568)
        at java.base/java.security.AccessController.doPrivileged(Native Method)
        at java.desktop/java.awt.Toolkit.getDefaultToolkit(Toolkit.java:567)
        at com.intellij.testFramework.TestApplicationManagerKt.replaceIdeEventQueueSafely(TestApplicationManager.kt:156)
        at com.intellij.testFramework.TestRunnerUtil.replaceIdeEventQueueSafely(TestRunnerUtil.java:12)
        at org.jetbrains.kotlin.test.testFramework.KtUsefulTestCase.runBare(KtUsefulTestCase.java:485)
        at junit.framework.TestResult$1.protect(TestResult.java:122)
        at junit.framework.TestResult.runProtected(TestResult.java:142)
        at junit.framework.TestResult.run(TestResult.java:125)
        at junit.framework.TestCase.run(TestCase.java:129)
        at junit.framework.TestSuite.runTest(TestSuite.java:252)
        at junit.framework.TestSuite.run(TestSuite.java:247)
        at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
        at org.jetbrains.kotlin.test.JUnit3RunnerWithInnersForGradle.run(JUnit3RunnerWithInnersForGradle.java:71)
        at org.jetbrains.kotlin.test.JUnit3RunnerWithInners.run(JUnit3RunnerWithInners.java:54)
        at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
        at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
        at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
        at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
        at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
        at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
        at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
        at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
        at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
        at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:121)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:564)
        at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
        at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
        at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
        at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
        at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
        at java.base/java.lang.Thread.run(Thread.java:844)

So I log to my

KSPLogger

but the text doesn't show up in my

./gradlew build

output. How do I change that? Or alternatively, where does the output show up?

ok finally got around to testing publishing a ksp processor with js support. It seems to work fine if the consuming project uses

js(LEGACY)

but it fails to run when it uses

js(IR)

. 🤔

Hi, one of the latest releases includes experimental support for KMP. Does this mean that I could generate code inside a Common module? If so, how would I do that?

would you ever consider allowing KSP to run embedded directly in kotlinc again? I understand why it's a separate task now, but I also wonder if that's something that could be configurable if none of the given processors require it. We're using Anvil pretty heavily (which wires into the same infrastructure) and the easy of just having it directly in the existing kotlinc tasks makes it really appealing to write new code generators using its infra rather than KSP

Could KSP be published to maven central too? This is a lot of headache for Dagger users to have to add a custom repo even if they’re not using KSP https://github.com/google/dagger/releases/tag/dagger-2.38

Where does files with extensions, other than

.kt

and

.java

, get placed, when crating them using CodeGenerator? Will they get included in apk (in android project)? Use-case: I would like to transfer processed info from one compilation module to another in this file (just text file), and use it while processing another module. Right now I just place this "transfer file" in

/module-name/build/generated/myProcessorName/transferFile

, but I have A LOT of problems with gradle: after

gradle clean

my processor doesn't run (presumably gets in gradle cache) and, consequently, doesn't produce this transfer file. In gradle logs I see

> Task :module-name:kspDebugKotlin FROM-CACHE

. Will this problem go away if I will use CodeGenerator to create this transfer file? If yes, how can I do so without including the transfer file in final build artifact (apk)?

playground is not part of our git history, we can check to see if there is any errors and update it

Are calls to

resolve()

cached? as in, if I do something like this:

a.resolve()
a.resolve()

Does this take double the amount of time, or is the second call much cheaper?

I feel like I don't understand incremental processing in KSP on a basic level. Say my processor uses class

A

by annotating

A

and calling ``resolver.getSymbolsWithAnnotation`, and I change class `B`(unrelated). Why does

process

get called? surely to save time it should not be called. At first I thought that

resolver.getSymbolsWithAnnotation

will return an empty sequence if only

B

was changed and

A

has not, but it does not. I get

A

in this invocation, and, at the end of the day, no time is saved and there is nothing incremental about this. So what exactly can be done to make processing code incremental? There is no flag

stuffHasNotChanged

.

We recently ran an experiment using KSP at airbnb I did some analysis on the results: https://docs.google.com/document/d/1zqQ5cMeucvAZtzN94YIcryvaNK_8KiJwF0Uyof4x5rw/edit# Quick summary: • ~660/900 modules were eligible to use ksp • KSP helped most builds by about 10% in most percentiles, but dropped the performance of P95 builds P95 drop in performance is likely from remote cache incompatibility and worse incremental compilation than kapt (ksp.incremental.intermodule=true just landed to address this)

Hi there! We are having a strange issue today where a generated

META-INF/services/xxx

(through

ServiceLoader

) with a KSP processor is not present on the final APK. I noted latest version has added this change: https://github.com/google/ksp/blob/1.5.21-1.0.0-beta06/gradle-plugin/src/main/kotlin/com/google/devtools/ksp/gradle/AndroidPluginIntegration.kt#L93 And seems to work on the test, but for some reason, it isn’t for us. It started working after I add this workaound:

android.applicationVariant.all {
            processJavaResourcesProvider.configure {
                from("$buildDir/generated/ksp/${this@all.name}/resources")
            }
        }

Any idea why

registerPostJavacGeneratedBytecode

may not be enough? I did played a bit with the

ksp

’s

AndroidIT

and it seems to work in there

Hi! I'm working on the Gradle plugin and symbol processor. The use of that plugin implies that the symbol processor should also be used. So I have decided to create yet another Gradle plugin to reduce all necessary repository, dependency etc configurations to one line. The question is: to make IDE aware of the generated code I would add something like this in my build file:

sourceSets {
   main.kotlin.srcDir("build/generated/ksp/main/kotlin/")
}

But should my plugin do this when applied to the project? Or should I leave this configuration to the end-user? I'm in such a dither over this because the KSP plugin itself doesn't add generated paths in source sets.

Given the type reference to functional type, how would you use it in generated code so everything is resolved? Right now i resolve reference to KSType and then recursively its type parameters. For plain functional types resolved name is FunctionN, and generated code with those works fine. But for

suspend () -> Unit

SuspendFunction

is unaccessible for user code :c So i think need something that converts

suspend () -> String

->

suspend () -> kotlin.String

. Just want to make sure not to reinvent the wheel.

Hi, here is the latest KSP release: 1.5.21-1.0.0-beta07 Highlights • starting this release, KSP binary has moved from gMaven to MavenCentral repo. • Kotlin native is now supported. • ksp.incremental.intermodule is enabled by default Issues resolved #60 Using KSP with Kotlin Multiplatform #411 Publish artifacts to be used with kotlinc command line #490 KspTask does not support gradle remote cache #240 java.lang.IllegalStateException: Cannot find descriptor for values #439 NPE #518 Configuration on demand does not work with KSP #540 Publish KSP on Maven Central? Please give it a try and let us know any thoughts!