-
Couldn't load subscription status.
- Fork 237
Version kotlinc plugins by major version to handle API changes. #1011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Allows reuse when defining kotlinc versions. Supporting multiple plugin apis will require supporting multiple kotlincs.
Managing multiple kotlinc version increases toil. To simplify things, introduce a centralized list of the support versions of kotlinc. Success for this is predicated on the plugin api remaining stable on point releases, which is anecdotally true.
This provides a separate plugin for each major kotlinc release. Still requires wiring into the toolchain system (follow up PR), but simplifies using older versions of kotlin with less effort.
Current stardoc cannot seem to handle dynamic key in dictionary comprehensions. The simple solution is to separate the KOTLINC_INDEX from the compiler repository definition. Has the added benefit of keeping development logic from production logic.
This was apparently skipped on previous passes.
| sha256 = "632166fed89f3f430482f5aa07f2e20b923b72ef688c8f5a7df3aa1502c6d8ba", | ||
| ), | ||
| ], | ||
| KSP_CURRENT_COMPILER_PLUGIN_RELEASE = version( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KSP also needs to be versioned to the Kotlin compiler.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, this is going to be fun.
Part one of two.
@nkoroste discovered we had been breaking backwards compatibility by updating the plugins as the compiler plugin api changes.
These separates and compiles each major version of the compiler plugins. The follow up pr will choose the correct plugin for the toolchain -- separating the efforts made sense form a complexity and limiting the scope of the PR point of view.