For targets specified under replacements, this makes the corresponding 3rdparty/jvm targets have public visibility.
This addresses behavior that I've found to be counterintuitive with strictVisibility enabled. I'd expect all dependencies declared in a dependencies.yaml to be visible to the workspace, regardless of whether it's under dependencies or replacements.
Fixes https://github.com/johnynek/bazel-deps/issues/173
For targets specified under
replacements
, this makes the corresponding3rdparty/jvm
targets have public visibility.This addresses behavior that I've found to be counterintuitive with
strictVisibility
enabled. I'd expect all dependencies declared in adependencies.yaml
to be visible to the workspace, regardless of whether it's underdependencies
orreplacements
.