Move the KSP and compiler target definitions into rules_kotlin #1014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some organizational changes to allow easier support for Bzlmod. This may introduce breaking changes for those that are depending on the targets declared directly inside of the
com_github_jetbrains_kotlin
/com_github_google_ksp
repositories.The new compiler target references can be found under the
@io_bazel_rules_kotlin//kotlin/compiler:...
package. We may start to reduce the visibility of these and ask users to eventually start pulling their standard libraries from maven.Details: With Bzlmod we are unable to easily import
kt_
macros from within a Bazel repository. To work around this we can shuffle the actualkt_
target creation intoio_bazel_rules_kotlin
instead of inside the declaredcom_github_jetbrains_kotlin
/com_github_google_ksp
repositories.