GitLab

Rather than using direct deps for javac compilation, use it only for
turbine header compilation. The javac compilation process requires many
potential transitive deps that will take a more comprehensive approach,
perhaps similar to bazel's reduced java classpath.

Turbine using direct deps would only affect annotation processors. In
particular, possibly Dagger. Building chrome_java with only turbine's
direct deps seems to have worked, but only removing more of the dirs
in the allowlist can determine if this works for the entire codebase.

Bug: 1092528
Change-Id: Ifc745d269ce8850a6c675458fcff25c46ca39937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2299531
Commit-Queue: Peter Wen <wnwen@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#788795}