Skip to content
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

Support Bazel rules_kotlin's toolchain without legacy providers #6394

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Apr 19, 2024

Support Bazel rules_kotlin's toolchain without legacy providers

This is a prerequisite to finally turn down legacy struct providers. The last such instance is used in rules_kotlin. And it's used to serve as integration with IntelliJ.

After this change, PR bazelbuild/rules_kotlin#1157 may be merged, keeping rules_kotlin working with IntelliJ.

Legacy struct providers have been deprecated by Bazel. Replacing them with modern providers, will make it possible to simplify and remove legacy handling from Bazel.

More info on: https://bazel.build/extending/rules#migrating_from_legacy_providers
Issue: bazelbuild/bazel#19467

@copybara-service copybara-service bot added the copybara-exported Added to PRs opened by copybara-service label Apr 19, 2024
@copybara-service copybara-service bot changed the title Support Bazel rules_kotlin toolchain without legacy providers Support Bazel rules_kotlin's toolchain without legacy providers Apr 19, 2024
@copybara-service copybara-service bot force-pushed the test_626344394 branch 2 times, most recently from e5e3097 to 5d30541 Compare April 23, 2024 12:24
This is a prerequisite to finally turn down legacy struct providers. The last such instance is used in rules_kotlin. And it's used to serve as integration with IntelliJ.

After this change, PR bazelbuild/rules_kotlin#1157 may be merged, keeping rules_kotlin working with IntelliJ.

Legacy struct providers have been deprecated by Bazel. Replacing them with modern providers, will make it possible to simplify and remove legacy handling from Bazel.

More info on: https://bazel.build/extending/rules#migrating_from_legacy_providers
Issue: bazelbuild/bazel#19467
PiperOrigin-RevId: 627353414
@copybara-service copybara-service bot merged commit 702227e into google Apr 23, 2024
0 of 3 checks passed
@copybara-service copybara-service bot deleted the test_626344394 branch April 23, 2024 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
copybara-exported Added to PRs opened by copybara-service
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants