Is KSP1 still being developed or are all efforts now on fixing issues in KSP2? I've added details to...

# ksp

[jamireh]

Is KSP1 still being developed or are all efforts now on fixing issues in KSP2? I've added details to a very annoying KSP1-only issue regarding FileAlreadyExistsException when incrementally compiling with Dagger KSP. Unfortunately, there are other KSP2 issues that prevent a migration at this time; the issue isn't with Dagger because the stracktrace is entirely in KSP but is more prevalent because it's an issue when generating Java code, which is all Dagger generates

I think it's a KSP1-only issue because I don't see references to shadow directories for generated Java sources in KSP2, which seems to be related

[Ting-Yuan Huang]

KSP1 is in maintenance mode. We spent most of the time on KSP2 because KSP1 depends on K1 / Kotlin 1.x.

Yes, the stacktrace you linked is KSP1 specific. It is specific to a workaround to a limitation that we have no control of certain compiler data structures in K1. The limitation doesn't exist in KSP2.

[jamireh]

👋 Gotcha, thank you for taking a look! Does maintenance mode include bugs like this or not really?

[Ting-Yuan Huang]

It depends on how bad and how urgent the bugs are. I cannot promise anything other than reviewing pull requests.

[jamireh]

Understandable, thank you!

[jamireh]

I think we'd rather migrate to KSP2 so the priorities make sense