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
For example, I've just spent a few hours trying to figure out why my test classes were not being properly named for their package (TLD of kiwi), in my specific case, tests in src/test/java/kiwi/**/*. All country-code TLD based packages would fail too.
Bazel itself appears to use a heuristic based on the maven-style layout of a prefix of src/test/java/ which is even noted in a comment!
The simplest mitigation is probably to allow the prefix to be specified in the rule. E.g.
https://github.com/bazel-contrib/rules_jvm/blob/0bef82e8d7038a6628faad06b9a57d10e536c2c5/java/private/package.bzl#L2C1-L2C72
The implementation is fundamentally flawed.
For example, I've just spent a few hours trying to figure out why my test classes were not being properly named for their package (TLD of
kiwi
), in my specific case, tests insrc/test/java/kiwi/**/*
. All country-code TLD based packages would fail too.Bazel itself appears to use a heuristic based on the maven-style layout of a prefix of
src/test/java/
which is even noted in a comment!The simplest mitigation is probably to allow the prefix to be specified in the rule. E.g.
The text was updated successfully, but these errors were encountered: