2016.2?

yup, latest bug fix update

@User uploaded a file: and commented: Same problem

Wait, I am using Gradle, it uses this version of Kotlin: 1.1.0-dev-2053

Perhaps the difference lies there?

Using 2615

let me try 2053

@User uploaded a file: and commented: Didn’t fix it

The version of the plug-in seems to say “2016.1”, does it matter it’s being used with 2016.2?

It's the same with me

I get fewer errors with 2053 though, so I think it’s the right path

however I need some pretty bleeding edge stuff in the scripting package

EAP build

1.0.4-eap-114

is available: https://discuss.kotlinlang.org/t/kotlin-1-0-4-eap/1901/4?u=tsvetkov

sorry,

kapt2

still doesn’t work

Ran into a kapt2 issue with eap 114, reported here: https://youtrack.jetbrains.com/issue/KT-13798

Is it possible to publish kapt2 related bugfixes a bit more often? It's third time in a row that EAP fails to build our project because of kapt bug and I'm almost 100% sure we will find more bugs in the future builds. Our project isn’t open source, but I'm ready to collaborate with the team and test dev builds almost every day just to speed up the process.

@michaelsims starred that, still holding off on Kapt2 haven't had a build with it yet 😄

Would love to get it working tho so 👍 on more rapid eap releases.

About the exception problems I was talking about yesterday: I just found out that there is a

kotlin.Throwable

class and it gets picked over

java.lang.Throwable

, which explains all the weird errors I was reporting (can’t find

ex.stackTrace

, etc…). So again, all points to

java.lang.*

no longer being implicitly imported

@User uploaded a file: and commented: Why would I use

kotlin.Throwable

when it’s missing most fields from

java.lang.Throwable

?

Cool that you found the issue!

“found” is overstating it, I’m still running with a completely broken environment with 1.1-eap 🙂

Still strange that I'm not getting the same issue though

@denis.zharkov ^^

@vmironov every change is run through CI on our TeamCity server, so you can get it daily, if you wish. You might need to setup some maven repo locally, though, if your infra depends on it.

Building Android apps/libs (including Dagger2) using Android Gradle plugin 2.2.0-rc2, Gradle 3.0, Kotlin 1.0.4-eap-100, kapt2

Fails on 1.0.4-eap-114

@cedric Is it just IJ complaining, or is it the Kotlin compiler itself? If IJ, try invalidating caches...

@orangy how would one setup usage of daily eap builds? Does this also work for 1.1?