For those of you who have gone through the migrati...
# compilerm
mattinger
07/15/2025, 5:05 PMFor those of you who have gone through the migration process to the K2 compiler, what did you do about KAPT based plugins? I'm working on removing it as much as I can, but i'd rather not have the compiler fallback to language version 1.9 just because of kapt. I'm mostly encountering issues related to legacy code with databinding enabled.
Copy code
w: Kapt currently doesn't support language version 2.0+. Falling back to 1.9. Copy code
w: K2 kapt is an experimental feature. Use with caution.z
Zac Sweers
07/15/2025, 9:13 PMK2 kapt works great for us
t
toadzky
07/15/2025, 9:13 PMusing ksp instead is the general recommendation i've seen
m
mattinger
07/15/2025, 9:15 PMThanks @Zac Sweers. Like I said, it's mostly data binding. That's the issue. The life cycle compiler works under KSP. And I'm using your plug-in for the auto value processor under KSP.
mattinger
07/15/2025, 9:16 PMAs well as the forked anvil compiler
z
Zac Sweers
07/15/2025, 9:16 PMyah we've had no issues with K2 kapt since kotlin 2.1. It was also a good deal faster
m
mattinger
07/15/2025, 9:16 PMI think we're still on the 2.0 plug-in but we should be updating that soon. The guy who normally handles that is on vacation