Hello. Testing Android gradle plugin 2.2 RC1 with Jack and wonder is somewhere this issue is tracked:

Cannot cast object 'task ':app:transformJackWithJackForDevDebug'' with class 'com.android.build.gradle.internal.pipeline.TransformTask_Decorated' to class ‚org.gradle.api.tasks.compile.AbstractCompile‘

? Disabling

kotlin-android

fixes it.

looks like https://youtrack.jetbrains.com/issue/KT-13275

I haven’t been keeping up with the EAP because I’m a bad citizen. Just tried switching, and I’m seeing this:

>> Could not find org.jetbrains.kotlinkotlin android extensions1.0.4-eap-118

is that a problem on my end, or did kae move, or is it just not part of the eap?

nvm, missing the bintray url apparently

@loganj the artifact exists https://bintray.com/kotlin/kotlin-eap/kotlin/1.0.4-eap-118#files/org/jetbrains/kotlin/kotlin-android-extensions/1.0.4-eap-118

thanks, I found it. Asked too soon… I was just missing the maven repo in my build.gradle.

another question: do EAPs have a timebomb in them? if I reference 1.0.4-eap-118 in my build, will I still be able to reproduce that build in two years?

(asking b/c android tools alphas do have a timebomb)

no, there is no timebomb

wonderful, thank you

Android tools have w tomb bomb? What's that for?

preventing people from using ancient, pre-release versions

ie reducing support costs.

On the recent exception Android Studio suggest me to send a report to Google, not to JB, but the stack trace contains these lines:

null
java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
	at java.util.ArrayList$Itr.next(ArrayList.java:851)
	at com.google.common.collect.AbstractMapBasedMultimap$WrappedCollection$WrappedIterator.next(AbstractMapBasedMultimap.java:486)
	at org.jetbrains.kotlin.resolve.BodyResolver.computeDeferredTypes(BodyResolver.java:886)
	at org.jetbrains.kotlin.resolve.BodyResolver.resolveBehaviorDeclarationBodies(BodyResolver.java:111)

Should I trust to the decision of the reporting tool and send it to the Google? // 1.0.4-eap-118-lj143-104

I think the report will actually get sent to us

is there a plan to merge new

kapt

to

1.1.0-dev

?

yes, of course

@adambl4 It’s already there

@yan should I enable it somehow? I'm on

1.1.0-dev-2984

and I see that

Realm

is processing annotated classes every launch

What do you mean? Annotations will be processed each Kotlin compilation, yes.

thanks, got it working. it seems

gradle-3.1-rc-1

doesn't support incremental compilation

@User uploaded a file: Method references and commented: Playing around with 1.1 EAP. I noticed method references doesn't quit work the same as its Java 8 counterpart, even after setting Kotlin's JVM target to 1.8

bar2

is perfectly fine, injecting the

foobar(1)

directly into the call site. However,

bar

still creates an annonymous instance of

Function1

. Inlining doesn't seem to work here at all Java 8's bytecode on the other hand uses

INVOKEDYNAMIC

for both lambda and method references.

^ @udalov

@kingsley inlining here has been fixed since 1.1-M1 and is going to be available in the next milestone

Oh. Good to know. Thank you

How soon is the M1 going to be available?

I mean M2

I’m not aware of any plans regarding M2

Okay then. Thanks anyway. I probably shouldn't get my hopes high for the 1.1 release anytime soon 🙂