You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
For some reason the Kotlin maven plugin (specifically kapt) isn't running correctly - it either processes teh dagger annotation processor in addition to javac doing so, OR (if we exclude the javac build) it doesn't seem to process.
I'm not at Google anymore, as of today, but I"ll try to roll a fix and secure the help of googlers to upstream it.
The text was updated successfully, but these errors were encountered:
@ngzhian - I'll try to coordinate with you once I've figured it out. Hopefully it'll just be pom changes which are trivial to diff/patch into google's internal codebase.
Hey @cgruber heads up, we reverted the kotlin stuff internally, but didn't push it out yet, your work will diverge, i don't know what's the story there yet...
Ok. I have a totally separate PR to bazelize which I finally figured out and fixed all the kotlin stuff too. I'm wondering if we want to keep these in sync, or if I should just perma-fork.
For some reason the Kotlin maven plugin (specifically kapt) isn't running correctly - it either processes teh dagger annotation processor in addition to javac doing so, OR (if we exclude the javac build) it doesn't seem to process.
I'm not at Google anymore, as of today, but I"ll try to roll a fix and secure the help of googlers to upstream it.
The text was updated successfully, but these errors were encountered: