-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
package(default_visibility=X) differs from visibility=X #13681
Comments
So the problem is that |
…ependencies to some scopes Note that using package default_visibility doesn't always work so explicit visiblity attributes are needed bazelbuild/bazel#13681 Somewhat related to bazel-contrib#648 In combination this for example allows to create a class_name -> maven artifact resolver for transitive dependency classes while still keeping strict visibility (making transitive dependencies visible only to the resolve cli tool)
…ependencies to some scopes Note that using package default_visibility doesn't always work so explicit visiblity attributes are needed bazelbuild/bazel#13681 Somewhat related to bazel-contrib#648 In combination this for example allows to create a class_name -> maven artifact resolver for transitive dependency classes while still keeping strict visibility (making transitive dependencies visible only to the resolve cli tool)
…ependencies to some scopes Note that using package default_visibility doesn't always work so explicit visiblity attributes are needed bazelbuild/bazel#13681 Somewhat related to bazel-contrib#648 In combination this for example allows to create a class_name -> maven artifact resolver for transitive dependency classes while still keeping strict visibility (making transitive dependencies visible only to the resolve cli tool)
…ependencies to some scopes (#649) Note that using package default_visibility doesn't always work so explicit visiblity attributes are needed bazelbuild/bazel#13681 Somewhat related to #648 In combination this for example allows to create a class_name -> maven artifact resolver for transitive dependency classes while still keeping strict visibility (making transitive dependencies visible only to the resolve cli tool)
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 or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please post |
Description of the problem / feature request:
package(default_visibility = X)
works differently from explicitly settingvisibility = X
Namely
visibility=
can refer to other@repository//some:__pkg__
, butdefault_visibility
ignores such entries.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
A/WORKSPACE
A/BUILD
B - empty directory
but if line 1 is commented out in A/WORKSPACE and line 2 uncommented all 3 build commands suddenly start to work
What operating system are you running Bazel on?
NixOS
What's the output of
bazel info release
?release 4.1.0- (@non-git)
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.via NixPkgs
The text was updated successfully, but these errors were encountered: