Print warning if class ids differ #185
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
|
@Godin @mfriedenhagen Please feel free to add your review comments, thx! |
marchof
added a commit
that referenced
this pull request
Jan 23, 2014
Print warning if class ids differ
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A frequent problem of JaCoCo users are classes showing 0% coverage while the classes are expected to be executed. In most cases this is caused by the fact that different classes are used at report generation time and at runtime.
Therefore the report and check tasks/goals should issue warnings, if the execution data does not contain a class with the same id but with the same name.
Also the core API should allow to provide such warning also in other tools see jacoco/eclemma#74