david.bilik
02/02/2017, 10:17 AMloganj
02/17/2017, 1:47 PMgildor
02/22/2017, 1:03 AMCompile-avoidance is deactivated if annotation processors are found on the compile classpath
and few lines below there is code example how to register AP configuration to exclude dependencies with AP from compile classpath.
And my question is: should it work with kapt out of the box, or should I register kapt by the same way how in release notes example?
Incremental compilation of Kotlin is significantly improved our build time.
And, because we still have a lot of Java code, It’s just important thing for our project, to achieve incremental Java compilation too. actually what Kotlin IC is doing, even when AP is used in project. Because old Gradle Java IC is disabled if you project contains AP.yan
03/07/2017, 1:53 PMyan
03/15/2017, 12:44 PMthemarketka
03/23/2017, 4:56 PMerror: cannot find symbol import com.packagename.SomeActivity_;
kapt3, kotlin 1.0.7: fails build, shows the same error
kapt3, kotlin 1.1.1: same
(using androidannotations and otto)pavlospt
03/27/2017, 11:45 AMsnowe
03/31/2017, 1:43 PMpavlospt
04/03/2017, 8:16 AMjw
04/16/2017, 4:25 AMjw
04/19/2017, 1:10 PMspierce7
05/25/2017, 1:28 AMyigit
05/29/2017, 2:40 AMgw --no-daemon :r:in:k:asDeb -Dkotlin.daemon.jvm.options="-Xdebug,-Xrunjdwp:transport=dt_socket\,address=5005\,server=y\,suspend=y"
after killing both daemons. I can connect, get a thread dump etc but it does not stop in breakpoints.
I tried, suspend=n
, does not help.
I've also tried -Dkotlin.compiler.execution.strategy="in-process"
to debug in gradle process but in that case daemon crashes.greenrobot
06/01/2017, 7:46 PMorg.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':tests:xxx-kotlin-test'.
caused by
kotlin.TypeCastException: null cannot be cast to non-null type org.jetbrains.kotlin.gradle.internal.WrappedVariantData<*>
at org.jetbrains.kotlin.gradle.internal.Kapt3KotlinGradleSubplugin.createKaptKotlinTask(Kapt3KotlinGradleSubplugin.kt:260)
at org.jetbrains.kotlin.gradle.internal.Kapt3KotlinGradleSubplugin.apply(Kapt3KotlinGradleSubplugin.kt:150)
at org.jetbrains.kotlin.gradle.internal.Kapt3KotlinGradleSubplugin.apply(Kapt3KotlinGradleSubplugin.kt:54)
at org.jetbrains.kotlin.gradle.plugin.SubpluginEnvironment.addSubpluginOptions(KotlinPlugin.kt:679)
at org.jetbrains.kotlin.gradle.plugin.Kotlin2JvmSourceSetProcessor$doTargetSpecificProcessing$1.execute(KotlinPlugin.kt:121)
at org.jetbrains.kotlin.gradle.plugin.Kotlin2JvmSourceSetProcessor$doTargetSpecificProcessing$1.execute(KotlinPlugin.kt:93)
at org.gradle.internal.event.BroadcastDispatch$ActionInvocationHandler.dispatch(BroadcastDispatch.java:89)
jw
06/10/2017, 4:29 AM00:11:21.355 [DEBUG] [org.gradle.api.Project] [KOTLIN] kapt: Discovered annotation processors: com.google.auto.service.processor.AutoServiceProcessor
00:11:21.355 [DEBUG] [org.gradle.api.Project] [KOTLIN] kapt: Stub annotation generated: /Users/jw/dev/square/cash/thing-processor/build/tmp/kapt/main/wrappers/__gen/KotlinAptAnnotation.class
00:11:21.356 [DEBUG] [org.gradle.api.Project] [KOTLIN] kapt: Wrapper for com.google.auto.service.processor.AutoServiceProcessor generated: /Users/jw/dev/square/cash/thing-processor/build/tmp/kapt/main/wrappers/__gen/AnnotationProcessorWrapper_main_com_google_auto_service_processor_AutoServiceProcessor.class
and then the compiler args
-processor __gen.AnnotationProcessorWrapper_main_com_google_auto_service_processor_AutoServiceProcessor -s /Users/jw/dev/square/cash/thing-processor/build/generated/source/kapt/main -Akapt.annotations=/Users/jw/dev/square/cash/thing-processor/build/tmp/kapt/main/wrappers/annotations.main.txt -Akapt.kotlin.generated=/Users/jw/dev/square/cash/thing-processor/build/tmp/kapt/main/kotlinGenerated /Users/jw/dev/square/cash/thing-processor/build/tmp/kapt/main/java_src/__gen/annotation/Cl.java
codeprogression
06/13/2017, 4:02 PMkapt
always be required? IOW, will it ever transition to using annotationProcessor
?
kapt "com.google.dagger:dagger-compiler:$daggerVersion"
//vs
annotationProcessor "com.google.dagger:dagger-compiler:$daggerVersion"
Eugenio
06/16/2017, 8:57 AMyan
06/21/2017, 3:30 PMyan
07/12/2017, 7:02 PMkapt.generateStubs = true
just allows you to use generated references in Kotlin code.yan
07/31/2017, 7:47 PMjw
08/04/2017, 3:59 PMyan
08/22/2017, 2:42 PMmannodermaus
08/25/2017, 8:39 AM@kotlin.Metadata
isn’t detectable from the processor’s environment.
This guy has had a similar issue: https://discuss.kotlinlang.org/t/kotlin-data-classes-inspection-from-annotation-processor/2163vmironov
08/29/2017, 2:11 PMerror.NonExistentClass
during incremental builds after upgrading to 1.1.4
. Cleaning the project solves the problem, but it makes kapt
completely unusable. We were forced to downgrade to 1.1.3
.mzgreen
08/31/2017, 7:33 AMsimon.vergauwen
09/02/2017, 9:54 AMmannodermaus
09/04/2017, 12:01 PMassertThat(kotlinc().compile(...)).suceeded()
lasse
09/27/2017, 7:12 AMuhe
09/27/2017, 7:39 AMbdawg.io
10/24/2017, 9:24 PMbdawg.io
10/24/2017, 9:24 PM