Avoid compilation failure(NonExistentClass) by kapt

[yoshidan]

Dagger-compiler cause CompletionFailure when trying to create "InjectionSite"

 com.sun.tools.javac.code.Symbol$CompletionFailure: error.NonExistentClass

I' d like to resolve this problem.

---

Kolin compiler generate stubs and before the annotation processor run.

ex)
here is original source code.

class AppStartActivity {
   @Inject
   override lateinit var activityPresenter: AppStartActivityPresenter
   
   lateinit var mBinding: ActivityAppStartBinding
}

here is stub code generated by kotlin compiler.
the type of databinding or other code that will be generated by apt is "error.NonExistentClass"

public class AppStartActivity {
   @field:javax.inject.Inject protected open lateinit var mPresenter:AppStartActivityPresenter
   public final lateinit var mBinding: error.NonExistentClass
  

here is compiled java code.

public class LoginActivity {
    private error.NonExistentClass mBinding
    private AppStartActivityPresenter mPresenter
    protected void setMPresenter(mPresenter:AppStartActivityPresenter)
    public void setMBinding(error.NonExistentClass)
    ...

After generating stubs kotlin annotation processing tools(kapt) run and.
but dagger-compiler cause CompletionFailure when trying to create "InjectionSite" for "setMBinding"

 com.sun.tools.javac.code.Symbol$CompletionFailure: error.NonExistentClass

because dagger-compiler try to create "InjectionSite" for all public method even if the method doesn't have "@Inject" annotation.

I think dagger-compiler doesn't need to create "InjectionSite" for the method that doesn't have "@Inject".

[ronshapiro]

I think this is a bug for kapt to deal with, not Dagger. Can someone with knowledge of Kotlin+kapt provide more insight?

Unfortunately, we don't have any infrastructure to test with kapt. It would be ideal to have tests to make sure we don't break this in the future.