incompatible_stop_exporting_language_modules #19455
Assignees
Labels
incompatible-change
Incompatible/breaking change
migration-ready
Incompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green
Comments
comius
added
incompatible-change
This was referenced Sep 29, 2023
shs96c
added a commit
to shs96c/rules_jvm_external
that referenced
this issue
Jan 5, 2024
This prepares rules_jvm_external for bazelbuild/bazel#19455 Closes bazel-contrib#967 which has been left in limbo.
shs96c
added a commit
to bazel-contrib/rules_jvm_external
that referenced
this issue
Jan 15, 2024
This prepares rules_jvm_external for bazelbuild/bazel#19455 Closes #967 which has been left in limbo.
martis42
added a commit
to martis42/rules_python-fork
that referenced
this issue
Apr 14, 2024
Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455 This elevates rules_cc from a dev dependency to a full dependency of rules_python.
martis42
added a commit
to martis42/rules_python-fork
that referenced
this issue
Apr 14, 2024
Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455 This elevates rules_cc from a dev dependency to a full dependency of rules_python.
martis42
added a commit
to martis42/rules_python-fork
that referenced
this issue
Apr 28, 2024
Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455 This elevates rules_cc from a dev dependency to a full dependency of rules_python. We need to add rules_cc to the internal deps as it has to be loaded before stardoc. Otherwise, a too old rules_cc version is used when using the legacy WORKSPACE setup
martis42
added a commit
to martis42/rules_python-fork
that referenced
this issue
Apr 29, 2024
Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455 This elevates rules_cc from a dev dependency to a full dependency of rules_python. We need to add rules_cc to the internal deps as it has to be loaded before stardoc. Otherwise, a too old rules_cc version is used when using the legacy WORKSPACE setup
martis42
added a commit
to martis42/rules_python-fork
that referenced
this issue
Apr 29, 2024
Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455 This elevates rules_cc from a dev dependency to a full dependency of rules_python. We need to add rules_cc to the internal deps as it has to be loaded before stardoc. Otherwise, a too old rules_cc version is used when using the legacy WORKSPACE setup
github-merge-queue bot
pushed a commit
to bazelbuild/rules_python
that referenced
this issue
Apr 29, 2024
Adds dependency on rules_cc 0.0.9 for both bzlmod and workspace This elevates rules_cc from a dev dependency to a full dependency of rules_python. Work towards incompatible_stop_exporting_language_modules, see bazelbuild/bazel#19455
|
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale. |
github-actions
bot
added
the
stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The flag requires providers and language specific modules to be loaded from their repositories. For example
JavaInfoandjava_commonneed to be loaded from@rules_java.This is required for the migration of language specific modules into their repositories.
The text was updated successfully, but these errors were encountered: