So I m not sure what the current status is are we currently

Question

So I m not sure what the current status is are we currently supposed to use `apply plugin kotlin kapt ` or is it an experimental thing I mean you can use `kapt` dependencies even if you don t do it but it works differently it seems which is a bit confusing Any clarification on this would be much appreciated slightly smiling face

igoticecream · Answer

< bod> kapt is the apt or annotationProcessor for kotlin it is used to generate code at compile time based on annotations for things like dagger and butterknife

bod · Answer

Yes I understand that but it seems that you can use `kapt` dependencies in gradle project even if you don t use the `kotlin kapt` plugin And if you do use this plugin you get a different version of `kapt` Is this correct

lovis · Answer

yes `kotlin kapt` is kapt3 Works well for us

bod · Answer

< lovis> Ok so if you don t apply the plugin you get an older `kapt` Like v2 Whereas if you use it you get `kapt3`

lovis · Answer

yeah

bod · Answer

ok thanks And do you use `generateStubs` This seems to be optional or not depending on which version wink

lovis · Answer

no you are not allowed to use that with kapt3

lovis · Answer

i think its supposed automatically fall back to an older kapt version if you use that but for me it simply didn t compile

bod · Answer

hmm interesting

bod · Answer

do you use Dagger by any chance The reason I m asking is that I think the generated stubs are incorrect public fields end up private

lovis · Answer

yes I m using dagger I don t have issues like that Maybe clean build helps slightly smiling face

lovis · Answer

``` compile com google dagger dagger $dagger version kapt com google dagger dagger compiler $dagger version ```

bod · Answer

I suppose you use `lateinit` for your injected fields In this case they are correctly public

lovis · Answer

yes that s right

lovis · Answer

so what are you doing ` Inject var myField Thing = null` or are you using `notNull` delegate

bod · Answer

that s right ` Inject var myField Thing = null` of course it makes more sense with `lateinit` slightly smiling face But this should work anyway so I think it s a bug

lovis · Answer

I think so too arrow left this guy seems to have a similar issue maybe file a bug or ask whether it s known first in < C0922A726|general>

bod · Answer

ok will do slightly smiling face Thanks