tree 817eadd352c3303f1809c6e78833fc2234c5d778
parent 85c77fefc453547bffa662b219a9bb5e75d576e8
author elenairina <elenairina@google.com> 1550597704 -0800
committer Copybara-Service <copybara-worker@google.com> 1550597816 -0800

Enable coverage for executing a java binary with --experimental_java_coverage.

When using --experimental_java_coverage coverage was not collected after building a java deploy jar in coverage mode and executing the corresponding binary (see Example 1 below). The identified issues:

1) JacocoCoverageRunner did not know it has to use the new implementation. It decides whether to use the new implementation based on the suffix of JACOCO_METADATA_JAR, which is unset in this case. To solve this we now set an environment variable in the java_stub_template to mark if the new implementation is used or not.

2) JarInputStream could not see the entries in the deploy jar. I fetched the entries directly from the JarFile instead.

Example 1)
bazel build --collect_code_coverage --experimental_java_coverage //java/main:main_deploy.jar
JAVA_COVERAGE_FILE=java_coverage.dat bazel-bin/java/main/main --singlejar

RELNOTES: None.
PiperOrigin-RevId: 234617047