diff options
author | 2017-11-03 21:00:03 +0100 | |
---|---|---|
committer | 2017-11-06 20:20:15 +0100 | |
commit | f675cb77cbd9a7290a0e5b4c71f0de1a09d71c62 (patch) | |
tree | e0c0c0cd0c78574e35843f87c4dac4f4c0a8b513 /src/test/java/com/google/devtools/build/android/ParsedAndroidDataTest.java | |
parent | fecf464ec3bf2593e31fa6cd25a45ce149c2dd75 (diff) |
Tweak java runfiles resolution.
Building a binary rule does not generally ensure that the runfiles
trees of its transitive data dependencies are up-to-date, so it's
generally a bad idea to use a dependency's runfiles tree from the
primary target. See https://github.com/bazelbuild/bazel/issues/3919
for an example of the problems this can cause.
This CL ensures that we pick the primary target's runfiles tree when
executing a java_binary from a runfiles tree.
This makes the Java runfiles path resolution similar to that of the
Python rules. (See commit [1].)
[1] 58ee85afcab07374dabc5493c780cbe3369b644f ("Don't follow symlink when looking for python module space")
Change-Id: I412ede5cf02ab2c407e45a2b262442ca67df9ba6
PiperOrigin-RevId: 174501597
Diffstat (limited to 'src/test/java/com/google/devtools/build/android/ParsedAndroidDataTest.java')
0 files changed, 0 insertions, 0 deletions