You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
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:
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.
The text was updated successfully, but these errors were encountered:
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:
It would be helpful for users if a hint could be shown in such situations:
The text was updated successfully, but these errors were encountered: