but we haven't changed the Android tools and it's building with 1.1.1 so...

oh, nevermind! it turns out that manually deleting all the

build

folders fixed it!

./gradlew clean

is your friend in many cases 😉

that wasn't enough

I had to

rm -Rf ./build ./*/build

@kirillrakhman I think it's time to migrate to kapt3

I would if it wasn't so sloooow

and supported incremental compilation

@yan ^^

Can we declare 1.1.3 the "make android builds fast again" update?

that's after adding a single blank line

Total time: 23.96 secs
Task timings over 50ms:
    124ms  :blsAndroid:resolveDevMultidexLollipopDebugDependencies
    117ms  :blsAndroid:mergeDevMultidexLollipopDebugResources
  14416ms  :blsAndroid:kaptDevMultidexLollipopDebugKotlin
   1006ms  :blsAndroid:compileDevMultidexLollipopDebugKotlin
   3979ms  :blsAndroid:compileDevMultidexLollipopDebugJavaWithJavac
    156ms  :blsAndroid:copyDevMultidexLollipopDebugKotlinClasses

and that's without dexing and packaging, only

compileSources

Again? 🙂 They’ve never been fast

they're actually pretty fast if you don't use kotlin at all 😞

ot kapt for that matter

I would say if you don’t use kapt

yeah

as workaround: i temporarily disable kapt when don't touch annotations related code

Just checked compilation of our project after changing a single line of code that shouldn’t trigger kapt

Total time: 47.918 secs

There is an ongoing top-priority activity on Kotlin performance, both in compiler and IDE. Some small improvements may be published in 1.1.* builds, but some things are too big (and risky) to do in patch update and will be available in 1.2

Honestly I don’t know how it will affect kapt, here @yan could tell more.

my point is: if you want people to stop using kapt1, kapt3 should become at least as fast as kapt1

I wonder, do you really have fastest perf with kapt1 ?

I switched to kapt2 and 3 because kapt1 was slow for me, but I never really thought about it

As a result I stopped using AP on my new projects

@kirillrakhman Can you share the detailed kapt performance metrics for an incremental build? You can get it if you add the

kapt.verbose=true

line in

gradle.properties

and launch the build with the

--debug

option

sure

📣 📣 📣 We're happy to announce the EAP for Kotlin 1.1.2. https://discuss.kotlinlang.org/t/kotlin-1-1-2-eap/2457

does this actually break anything?