Open drigz opened 6 years ago
I had the same problem, also have no idea how to reproduce it, and bazel clean --expunge
fixed it.
I had the same problem too
I met this problem in following case: do NOT specify executable=True
in rule but return DefaultInfo provider with executable inside
Twice we have seen an error looking like this:
The missing jar is not always the same. Retrying the build doesn't help, but
bazel clean --expunge
does. Unfortunately I don't have a way to reproduce it, but it seems to happen when the system hasn't rebuilt the Java targets in a while (maybe due to changes in the version on Maven?)I know this isn't a very helpful bug report :) I'm posting in case anyone else is experiencing the same issue.