diff options
author | Martin Stjernholm <mast@google.com> | 2019-05-29 15:46:34 +0000 |
---|---|---|
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2019-05-29 15:46:34 +0000 |
commit | 90e2eef5125960b33374ee01eba30312bd9249f0 (patch) | |
tree | 4ce5f6d6cd88e79c742a4a669d6d51ede11d9ae1 /README.md | |
parent | 4b06c202158ec6fc01b3b8bdda03fa37a9d5a5be (diff) | |
parent | 226b20dc15457271a8174bc1c9d474e8435e3b68 (diff) | |
download | soong-90e2eef5125960b33374ee01eba30312bd9249f0.tar.gz |
Merge "Allow //visibility:public to override other visibility rules."
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -197,8 +197,10 @@ where `//project` is the module's package. e.g. using `[":__subpackages__"]` in * `["//visibility:legacy_public"]`: The default visibility, behaves as `//visibility:public` for now. It is an error if it is used in a module. -The visibility rules of `//visibility:public` and `//visibility:private` can -not be combined with any other visibility specifications. +The visibility rules of `//visibility:public` and `//visibility:private` can not +be combined with any other visibility specifications, except +`//visibility:public` is allowed to override visibility specifications imported +through the `defaults` property. Packages outside `vendor/` cannot make themselves visible to specific packages in `vendor/`, e.g. a module in `libcore` cannot declare that it is visible to |