Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incompatible_java_coverage: allow coverage collection for JVM languages #7425

Closed
iirina opened this Issue Feb 14, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@iirina
Copy link
Contributor

commented Feb 14, 2019

The option --incompatible_java_coverage:

  • makes possible collecting coverage for Starlark JVM languages and jars imported with java_import
  • only includes JVM files in the coverage report (dismisses data files, for example .js files that shouldn't have been in the report in the first place)
  • the report includes the actual path of the files relative to the workspace root instead of the package path (e.g. src/com/google/Action.java instead of com/google/Action.java). This allows genhtml to generate HTML reports from the combined bazel coverage output.

For more details see Bazel coverage for JVM languages.

Migration Notes

The users do not have to do any migration. Having the package paths in the report was filed as a bug (see #2528).

@iirina iirina self-assigned this Feb 14, 2019

@bazel-io bazel-io closed this in e64066d Feb 27, 2019

bazel-io pushed a commit that referenced this issue Apr 1, 2019

Remove --experimental_java_coverage/--incompatible_java_coverage flag.
RELNOTES: --experimental_java_coverage/--incompatible_java_coverage flag was
removed. See #7425.
PiperOrigin-RevId: 241342271

emusand added a commit to emusand/bazel that referenced this issue Apr 16, 2019

Enable --incompatible_java_coverage by default in Bazel.
Fixes bazelbuild#7425

RELNOTES: `--incompatible_java_coverage` is enabled by default.

Closes bazelbuild#7426.

PiperOrigin-RevId: 235914032

emusand added a commit to emusand/bazel that referenced this issue Apr 16, 2019

Remove --experimental_java_coverage/--incompatible_java_coverage flag.
RELNOTES: --experimental_java_coverage/--incompatible_java_coverage flag was
removed. See bazelbuild#7425.
PiperOrigin-RevId: 241342271
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.