You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining repository access with .netrc file it looks like jvm_maven_import_external is not using this. This is unexpected as .netrc should work everywhere in Bazel.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Create dependency consumption with jvm_maven_import_external from a password protected source.
Create .netrc file.
Which operating system are you running Bazel on?
No response
What is the output of bazel info release?
No response
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
release 5.1.0
What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered:
Description of the bug:
When defining repository access with
.netrc
file it looks likejvm_maven_import_external
is not using this. This is unexpected as.netrc
should work everywhere in Bazel.What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Create dependency consumption with
jvm_maven_import_external
from a password protected source.Create
.netrc
file.Which operating system are you running Bazel on?
No response
What is the output of
bazel info release
?No response
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.release 5.1.0
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: