Unable to access exported runfiles provided by library via a test

[mindscratch]

I have a library that provides code and data (called datalib). In a separate kotlin library called foo I create a target foolib that depends on //datalib. I create another kt_jvm_library named footest-deps that exports :foolib.

I then have a test that tries to use datalib (which reads data via Runfiles). If the test depends on :foolib it works, if the test depends on :footest-deps it fails to locate the data. It seems that a library which exports things doesn't allow/make the data from other libraries available.

To reproduce, clone this repo (tested with JDK17), and run bazel test //foo:AllTests. It will fail. If you modify foo/BUILD.bazel so the test depends on :foolib it will pass.

[restingbull]

Hm. Should go check on the java semantics out of curiosity.

But it does make sense that export would export the runfiles as well as classes.

[mindscratch]

@restingbull I added a java example jfoo which works whether the library it depends on is a regular library or one which exports another. See jfoo

[restingbull]

@restingbull I added a java example jfoo which works whether the library it depends on is a regular library or one which exports another. See jfoo

We usually lean towards rules_java as the source of truth, but this feels like a principal of least surprise thing.

[mindscratch]

Thanks, I'll look to try this out when the next release comes out.