Does anyone know why some generated files wouldn’t show up in the

generated/source/kapt

folder, even though they are being generated? (They’re in the AAR and final APK of my app)

hi everyone! we're running into problems in our android gradle builds because of NPEs being thrown from kapt. what is the best way to report such issues? 🙂

Hello, even I use

kapt{ annotationProcessor("foo.bar.Aprocessor") }

. The gradle show me that Can't find annotation processor. Before that, I use

kapt/compileOnly("com.google.auto.service:auto-service:1.0-rc7")

in the processor build file. And use

kapt/compileOnly(project("codegen", "default"))

in the parent project (which use the annotation in fact.) Thank you for your help.

Can I access Kotlin meta information from AnnotationProcessor? I think it's an useful feature. Is it useful? Thank you

What is the simplest way to debug a kotlin annotation processor?

Working on an Android library using Gradle, Kotlin and a 3rd-party codegen plugin using kapt, is there a way to have kapt generate sources but to prevent these files being included in the module build artifacts? I am hoping to be able to split the kapt output into a separate AAR (dependent on the original library), avoiding a trail of unnecessary dependencies for those who don't need the generated classes.

It breaks our compilation now with this example

interface ListOptionsInterface : Serializable {
    val caption: Int
}

@Parcelize
data class PreferenceOptionModel<T : ListOptionsInterface>(
        var options: T,
        var isSelected: Boolean = false
) : Parcelable

I can not also find details about this change in CHANGELOG

Should I move it to plugins? Should I delete it since I already found an issue and added comments

Hello, World! I'm trying to investigate which processors we're using that are not incremental. We used to have a warning about this, but I don't see it anymore. I'm kind of following this article[1] about this, so I'm enabling verbose logs and start a build like this:

./gradlew clean :app:assembleDebug -Pkapt.verbose=true --no-build-cache

I don't see the

Incremental KAPT support is disabled

log (I'm certain we used to have it some time ago). But I do see a bunch of

Incremental annotation processing (apt mode): false

which worries me. Does this mean it's disabled? (We do have

kapt.incremental.apt=true

in our

build.properties

). 💡 Ideas? [1] https://medium.com/@daniel_novak/making-incremental-kapt-work-speed-up-your-kotlin-projects-539db1a771cf

Hi All, I’m currently keep struggling with the error reports when using a Processor with KAPT and Gradle. When anything fails I’m only receiving a message like

FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':connector:example:connector-confluence-cloud:kaptKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution
   > java.lang.reflect.InvocationTargetException (no error message)

The processor has been written by myself, so I can change something on that end, but I’m not finding any solution for that. I keep logging using

processingEnv.error()

but can’t find any results in the actual log. Is there any way to improve the logging here? Thanks in advance!

what are the differences between

kapt

and

kaptKotlin

directories in

generated/source

? When should I use one or the other? Can't really find anything about it. Dagger and moshi seem to generate to

kapt

. From my tests it seems that I need to manually tell gradle where to look for these files for either of these (via

kotlin.srcDir("${buildDir.absolutePath}/generated/source/kapt/")

or

kotlin.srcDir("${buildDir.absolutePath}/generated/source/kaptKotlin/")

. Yet it doesn't seem to be necessary for dagger etc. If that makes any difference, I'm asking about kotlin multiplatform module.

Hello everyone! Could please anyone point me to a detailed documentation on how to use Kapt server side, possibly with maven? I found a lot of articles but they are all Android oriented....

hey there i'm trying to learn Kapt annotation processing. I have this toy project, with a

@TestAnnotation

, a

Hello

class annotated, and a

TestProcessor

that generates a new class named "<AnnotatedClassName>_Banana" with a method

eat

, in this case

Hello_Banana

. Everything is in place correctly, and from maven it works just fine. How should I let Intellij use the annotation processor as well? I tried like in the second screendshot but with no luck... Thank you in advance you for your help

Hi, is it possible to get the source file of the code where an annotation is used inside of an annotation Processor? So e.g. i do have the file main.kt and there is my annotation attached to the main function. Is it posiible to get the path and file name of that file inside of my Processor?

Not sure if this is the correct place to ask : I can't seem to get the incremental annotation processor to work w/ kapt. I'm setting 

kapt.incremental.apt=true

 in the props file but I get this message when gradle runs : 

Incremental annotation processing (apt mode): false

 I don't get any errors about processors that are not incremental. Any idea of where to look? I'm using kotlin & kapt version 1.4.32

Are there any library can resolve the default value of a parameter? Thank you. I know it might be an AST or something. I only need it for documents.

has someone a good tip for a kapt tutorial for serverside annotation processing? (Android is not involved in any way. The task is to generate a documentation file containing which classes contain certain annotations. Since it's Kotlin files we're talking about, I guess that kapt is the right tool for the job!?)

I’m using kapt to generate JPA metadata annotations. It works fine when I run it with JDK 15, but it fails with JDK 16. Any thoughts? I’m running it from maven, using the 1.5.0 kotlin plugin. Both jdks are AdoptOpenJDK.

Is there any way in 1.4+ to figure out why kapt is non-incremental for a build? I searched previous messages and people suggest downgrading to 1.3x which is basically impossible in our app

How do I make a simple annotation processor? No Android, just JVM, Kotlin, and Kapt. The only doc page I can find (https://kotlinlang.org/docs/kapt.html) doesn't really say anything about actually making a processor.

When kapt complains, that it can't find a

tools.jar

(which is correct, because I'm not using Java 8 anymore) – what doesn't work then? Any way to suppress that warning (I'm using Maven)?

Hello, i'm trying

kapt.classloaders.cache.size

option, and have really nice results: KaptWithoutKotlincTask: Found 243 tasks executed in 243 projects totaling 6m 59.605s (without cache) Found 243 tasks executed in 243 projects totaling 2m 3.507s (with cache) my question: is 250 a sane number for cache.size option? it says

# use the same value as the number of modules that use kapt

but something tells me that it might be an overkill, or it's ok?

Hi folks - I wrote a (potentially spicy) writeup requesting a roadmap for Kapt and voicing some concern about its seemingly adhoc current maintenance. I hope it lands well - https://youtrack.jetbrains.com/issue/KT-48661

hello guys, is anyone having this Issue?

java.lang.IllegalAccessError: class org.jetbrains.kotlin.kapt3.base.KaptContext (in unnamed module @0x50148e28) cannot access class com.sun.tools.javac.util.Context (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.util to unnamed module @0x50148e28

I am having this after update gradle to version 7.2…

This message was deleted.

Hey. can someone help to to understand what that means:

implementation fileTree(dir: "lib", include: "*.jar")

Execution failed for task ':kaptKotlin'.
> Could not resolve all files for configuration ':_classStructurekaptKotlin'.
   > Failed to transfor Some.jar to match attributes {artifactType=class-structure, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for StructureTransformAction: /lib/some.jar.
         > java.lang.IllegalArgumentException (no error message)

Is this a gradle or kapt issue?

Recently ran into an issue where someone accidentally reintroduced kapt into a module that we’d intentionally migrated fully onto KSP Is there a way to disable/block kapt so we can avoid similar issues in the future?

Maintenance mode doesn't inherently mean deprecated or discontinued or replaced. There are better and faster alternatives out there if you're willing to drop java support, but kapt was always about bridging java processors to kotlin

Does kotlin-kapt 1.6 support java 14?