feat: allow attaching platform constraints to dependency trees imported through maven.install #1298
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The user sets it in `MODULE.bazl`/`WORKSPACE` to affect `java_import` targets in the `maven.install` repo.
Necessary to use outbound transitions on Bazel versions prior to v7.1.
plobsing
force-pushed
the
targets_compatible_with
branch
from
fca5c52 to
b1fbc25
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Platform constraints can be used by users to enforce isolation between distinct dependency trees.
Users can choose which dimensions they care to isolate — OS, CPU, or even some custom definition
that only makes sense for their codebase.
Fixes 1222