[bazel] Adjust to moved bazel_tooling and neverlink domain classes#1862
Merged
Conversation
This is necessary to be able to swap in other domain classes since Bazel does not have an override functionallity like maven resolvers typically do. In order to achieve something similiar, the dependency needs to be marked as `neverlink` from the begining and each executable needs to bring in a linkable version on its own.
maltek
approved these changes
Jul 7, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is necessary to be able to swap in other domain classes since
Bazel does not have an override functionallity like maven resolvers
typically do. In order to achieve something similiar, the dependency
needs to be marked as
neverlinkfrom the begining and each executableneeds to bring in a linkable version on its own.