Open aherrmann opened 5 years ago
Here is the line.
That happens when we fail to resolve a declared jar. That shouldn’t be where we get the error but a better message could be added there: filter all the nodes we can’t find, print all of them and suggest to check the resolver.
A better fix would be to actually have Coursier error. Maybe this is a bug report for Coursier.
bazel-deps
does not handle invalid resolver URLs gracefully. For example, modifyingdependencies.yaml
in this repository as followsand running
bazel-deps
on its own repository generates the following error message:In particular, the error message doesn't mention the resolver at all.
cc @gdeest