Something with the classpath for unit tests must have changed in eap 69 compared to 44. My project c...

# eap

[ralf]

Something with the classpath for unit tests must have changed in eap 69 compared to 44. My project compiles fine with eap-44, but with 69 an annotation processor doesn’t find the class android/os/BaseBundle anymore.

Is this a know problem? I can workaround it by adding a testAnnotationProcessor 'dep' dependency

[h0tk3y]

@ralf Could you please share a project/example of how the problem can be reproduced?

[h0tk3y]

Also, what is the version of Android Gradle plugin?

[ralf]

2.4.0-alpha5, I’ll try to create test project later.

[h0tk3y]

Fine, thanks.

[ralf]

Found the issue. I was still using kapt1. With the kotlin-kapt plugin it’s working.

[h0tk3y]

@ralf We'd like to fix it for kapt1 as well, so we'd still appreciate the details on how it can be reproduced -- if it worked in eap-44, then we must have broken something.

[ralf]

Done: https://github.com/vRallev/android-state/tree/kotlin-eap

[ralf]

I described the problem in the README. Let me know if you need more information

[h0tk3y]

Many thanks, I'll look into soon.

[ralf]

Do you want me to create an issue?

[h0tk3y]

No need, thanks, I've already found what got wrong.

[ralf]

You’re great, thanks! But I’m curios, who’s fault is it?

[h0tk3y]

@ralf, in a nutshell, there has been a change in configuring annotation processing, and the order of items in -processorpath passed to javac has changed so that the classpath items now appear before the added processor classes. Seems like it only matters when there are multiple versions of the same class in the processor path. The solution is to revert the order and pass the classpath items last, as it was before.

[ralf]

Okay thanks

[h0tk3y]

@ralf The fix will be available in the 1.1.2 release (though it's not been shipped with any of the EAPs): https://github.com/JetBrains/kotlin/commit/e6e7f334bd9be0c714cba4c5cd15a2b61c41bb8f

[ralf]

Thanks for the info. I tested the latest EAP and noticed that it isn’t working, yet. But I’m glad that it’ll make it into the final release. Great support!