we see this pretty consistently in our project, anything I can do to help diagnose/rootcause it?

kotlin scripting plugin: applied in the non-supported environment (error received: Cannot query the value of task ':libraries:foundation:feature-flag:compiler:kspKotlin' property 'sourceSetName$kotlin_gradle_plugin' because it has no value available.)
kotlin scripting plugin: applied in the non-supported environment (error received: Cannot query the value of task ':libraries:foundation:carbonite:carbonite-compiler:kspKotlin' property 'sourceSetName$kotlin_gradle_plugin' because it has no value available.)

Hi, here is a minor release for kotlin 1.5.31: https://github.com/google/ksp/releases/tag/1.5.31-1.0.0 This release is only about bumping kotlin compiler version, otherwise identical to 1.5.30-1.0.0 release. If you are not updating kotlin version to 1.5.31, you can ignore this release.

When

aggregating

of

Dependencies

is set to

true

, will even file changes that are not related to a particular annotation be reprocessed?

val symbols = resolver.getSymbolsWithAnnotation("Factory")
symbols.forEach { symbol ->
    val ksClass = symbol as KSClassDeclaration
    val packageName = ksClass.packageName.asString()
    val className = ksClass.simpleName.asString()

    val file = codeGenerator.createNewFile(
        Dependencies(true, ksClass.containingFile!!), // <--
        packageName,
        "${className}Factory"
    )

    // generate code ...
}

We see this failure on Kotlin 1.6-M1, worth filing or known?

Caused by: java.lang.NoSuchMethodError: 'org.gradle.api.provider.Property com.google.devtools.ksp.gradle.KspTaskJvm.getUseClasspathSnapshot()'	
	at com.google.devtools.ksp.gradle.KspTaskJvm.configureCompilation(KspSubplugin.kt:511)	
	at com.google.devtools.ksp.gradle.KspGradleSubplugin$applyToCompilation$kspTaskProvider$1.execute(KspSubplugin.kt:335)	
	at com.google.devtools.ksp.gradle.KspGradleSubplugin$applyToCompilation$kspTaskProvider$1.execute(KspSubplugin.kt:330)	
	at org.gradle.api.internal.DefaultMutationGuard$2.execute(DefaultMutationGuard.java:44)	
	at org.gradle.api.internal.DefaultMutationGuard$2.execute(DefaultMutationGuard.java:44)

and related - would y'all consider mirroring Kotlin's milestone/rc releases too? We do extensive testing against preview releases and it would be a real bummer if we lost that ability with KSP. We've caught dozens of bugs early and been able to report them before stable release that way

are there any drawbacks of using

ksp

in a project that uses

kapt

for all other annotation processors? or is it that i just won’t see the speed improvements from using

ksp

?

is this the correct approach at pulling out an annotation argument?

parameter.annotations.firstOrNull { annot ->
    annot.annotationType.resolve().isAssignableFrom(annotationType)
}?.arguments?.firstOrNull()?.let { annotation ->
    foo = (annotation.value as? String)
}

i’m not used to casting like this, so just checking i’m not going down the wrong path

hey gang - in doing some searching I haven't seen this topic broached in a bit. is there any straightforward recipe for combining KSP with an android library? I've been trying to cram the

com.android.library

plugin into the KSP Quickstart's

test-processor

module without much luck

Hello ! Didn't find a way to define a unit test to validate my own compiler. Is there some documentation somewhere or a reference example by any chance?

FYI, Paris now supports KSP as of its recent 2.0.0 release. Implementation was done with XProcessing to keep compatibility with KAPT. If you’re interested you can see the changes at https://github.com/airbnb/paris

Looks like

Resolver.getSymbolsWithAnnotation

only returns annotations available in the same compilation/gradle module for KMP. When I move the annotation to another module (dedicated to annotations) it's not returned anymore. Have you already experienced something similar ?

as a general annotation processing question: how can i write unit tests for one? I can check the compilation output with the

kotlin-compile-testing

library, but I’m interested in testing the functionality. Is the best option to create a new module which depends on the annotation processor and run tests there?

I've noticed in our project that having both KSP and kapt enabled in a project results in corrupted incremental compilation data. Should I file an issue for this or would it fall under the category of "interop with kapt is undefined behavior"?

Playing with KSP on a multiplatform project, compilation is crashing because of multiple classesDirs (as I understand it). It's crashing in KotlinJsIrLink:l54 where the code use a .single() on a list that (I suppose) has the classes dir + the generated dir. Is my understanding correct and should I discuss this in multiplatform/JS instead?

Hi all! I was wondering, is checking if the app has some dependency a valid use case when using KSP? Like imagine, if the user of my KSP library has a certain dependency, then I want to generate some classes a bit differently? I seemingly managed to do this by calling

resolver.getDeclarationsFromPackage("com.some.package").iterator().hasNext()

, but I was wondering if there is a better/more performant way.

Hello! I ve created a KSP processor and everything goes fine! It generates the classes that I want. The problem is that I want to use it only during testing, so when I change ksp into kspTest the classes are not generated anymore. Is there any limitation/issue? Should I generate these classes in my app and let proguard do its job while having these classes accessible to my tests?

Hi guys - it seems like when I have a annotated data class in a function it is not getting recognized with

resolver.getSymbolsWithAnnotation

class Foo {
    fun bar() {
        @SomeKspAnnotation
        class Hello()
    }
}

I’m only doing this for a unit test, so i can work around it in my real code. just wondering if it’s a known issue

Is there a good blog post about migrating your custom annotation processor from kapt to ksp?

This might be already questioned elsewhere (not sure what was the keyword) Did we need to wait for library author to support KSP, or we can just replace

kapt

with

ksp

? 🙏

If I want to build a processor (and annotations to use with it) should those module apply the Kotlin jvm plugin, or multiplatform plugin?

Are there any guides/examples of ksp MPP processors and their usage?

Hello ! I've a KMP project with 2 modules, one define a class, the other defines an interface that returns the class from the other module. When processing the interface, I'm only able to retrieve the name from

func.returnType.toString()

but

resolve()

only returns empty/null/"<Error>". Is it something already known or covered by pull/609?

I noticed that kapt is set up to depend on KSP. In all our cases though, they have no dependencies. Is there a way to break this dependency so they can work in parallel?

Is there some ways to get the input kotlin file content directly? I'd use a regex on the file content to grab some imports as a workaround for the resolve() issue mentioned earlier.

Is there any way to run KSP before the

processManifest

task? KSP adds a dependency on the

processResources

task (which also depends on

processManifest

). I've tried to remove it from

dependsOn

but somehow it's never removed and I end up with cyclic dependencies. I want to generate a class with KSP and add a reference to it in

AndroidManifest.xml

for dynamic loading

Hi I'm trying to bother with KSP. I have a simple use case: deserialize line of Strings coming from a csv file to a data class with type conversion. It might be overpowered to do this with KSP, but I would like to use this chance to learn annotation processing etc. Can someone give me a blueprint how this mapping with conversion would look like on the basis of an example (not the glue, just the processing code)? Or is someone aware of an example that matches my use case?

Is it possible to analyze the code generated by KAPT with KSP?

given a

KSType

, how can I tell if it is an enum? i’m looking into obtaining a

KSClassDeclaration

for

Enum<*>

I'd like to implement the equivalent of an "around advice" aspect for some auditing functions. Is KSP a reasonable tool to use? If yes, are there any examples doing something similar that I can look at?

I’m finding that

resolver.getClassDeclarationByName

is not finding already compiled Java classes in a jar that is on the classpath. Is that expected? Using 1.5.30-1.0.0