Coverge support breaks when test has its own dependency on `org.jacoco.*`

Open
#202 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system, testing-qa

Research direction

Start by reproducing bazel coverage with a test or library that has an org.jacoco.* dependency, including the third-party dependency case described in the issue. Trace where the dependency is handled during compilation; done means the technical limitation is reported at compile time instead of coverage support silently breaking.

Written by the indexing model from the issue text.

Description

P3

As a coverage tool, it is highly unlikely that a library will include a genuine dependency on org.jacoco.*. However;

  • There are no safeguards in place. If this does happen, bazel coverage may just not work. Ideally what I suspect to be a technical limitation would be reported on at compile time.
  • Sometimes third party packages include test dependencies as compile dependencies by mistake. e.g. https://github.com/aliyun/aliyun-openapi-java-sdk/pull/930
Dominant language
Starlark
Stars
103
Forks
102
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bazelbuild/rules_java

All issues in bazelbuild/rules_java

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.