oops

It’s still there

=(

@cy how can I file a bugreport for another NonExistentClass issue? I don’t really understand which details can I provide

Or maybe some tips how to find the reason for this error

^^ @yan

I can try pushing my branch and giving you guys access to the project

@aaverin Do you use kapt with stubs in 1.0.4 eap 118?

yes I had a fully working project on 1.0.3 Then I decided to extract part of the project to another module and put as a library dependency. Made a module, moved files, did all the setup, tried syncing gradle and boom, NonExistentClass Now I tried Android Studio 2.2 and 1.0.4 eap hoping it would fix the problem, but now it’s on compile time, same error

The old way of fixing NonExistentClass didn’t work. Before it would most likely be somewhere in DI configuration classes If not - I would open every file one by one in search for a buggy import of missing files

@aaverin Hm, by the way, did you tried kapt2?

Not yet. So far I just moved my changes to a temp branch and rolled back

Will try eap without refactoring first 😃

how can I switch to kapt2?

Just add

apply plugin: ‘kotlin-kapt’

to the

build.gradle

file

Do I need to remove old

kapt generateStubs

?

It’s not needed anymore, though nothing really bad will happen if you leave it there

Ok, we are trying out migration to Android Studio 2.2 anyways, so will also try new kapt

Wow, that’s weird. Building in terminal with gradle on eap fails on extension properties with unresolved reference

Building in android studio works fine

Does anyone know when Kotlin

1.0.4

will be released?

I wouldn’t rush...

I’m trying kapt2 and I noticed that when I declare a dependency to a local project (in the format

kapt project(':annotations-processor’)

) that project gets compiled after the annotation processor runs, making it necessary to build twice to apply the changes - is that a know issue? (using

1.0.4-eap-118

)

I also get this error, not sure if it’s related:

Caused by: java.io.FileNotFoundException: JAR entry META-INF/services/javax.annotation.processing.Processor not found in /path/to/my/annotation/processor.jar

but if I run the old kapt it works fine (and I double check: the

Processor

file is in the jar)

@dmarcato Looks like something new. Can you please file an issue?

@yan I created https://youtrack.jetbrains.com/issue/KT-13999

@yan also this one 😅 https://youtrack.jetbrains.com/issue/KT-14000 (yay for issue #14000! 😛)

and I notice that you put

1.0.5

for `KT-13999`… are you guys freezing

1.0.4

or is it just not enough high in priority?

@dmarcato For now it’s just not clear if we will release updates for 1.0.4.