Skip to content
This repository was archived by the owner on Oct 1, 2020. It is now read-only.
This repository was archived by the owner on Oct 1, 2020. It is now read-only.

Warning about non-matching classes #113

@marchof

Description

@marchof

It seems to be a common problem, that exec files are imported into Eclipse executed with different class files. The same situation arises if tools like Powermock are used which modify classes at runtime. JaCoCo offers an API to detect such situations:

org.jacoco.core.analysis.IClassCoverage.isNoMatch()

It would be helpful for users if a hint could be shown in such situations:

  • Annotate classes with non matching exec data in coverage view (e.g. icon overlay)
  • Show disposable hint in coverage view if non-matching classes do exist. This could be tricky if different versions of the same class exist in the workspace. Here the hint should only be shown if non of them do match.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions