-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Improve error message in case of reading of old dump file #319
Conversation
@Godin Any proposal what would be more user-friendly? Some hint for resolution, e.g.
|
@Godin I also wonder whether JaCoCo should introduce a specific IOException (IncompatibleExecFileVersionException extends IOException) so Sonar could react in a more user friendly way? The general question is whether todays exec file format is the correct exchange format in the long run. Possible alternatives are:
|
This error message also alienated me, when coming across it while doing some For me, there are three issues with this error message
Bottom line: I'd replace the error message Incompatible version 1007 by Failed to read version 6 data (This JaCoCo build can only read/write version 7 data). To read the version 6 data, use the same JaCoCo version that got used for writing it. . I gave it a shot at #330 (along with the separate exception class brought forward by @marchof). |
Jacoco last version I installed :jacoco-0.7.6-20150603.214955-4 I installed EclEmma jacoco plugin today. |
In case of incompatible execution data formats read from another JaCoCo version ExecutionDataReader.read() now throws a IncompatibleExecDataVersionException with a better error message.
Improve error message in case of reading of old dump file.
Speaking on behalf of @benzonico, who maintains JaCoCo integration with SonarQube:
Indeed, this message is hard for understanding by end-users, while it can reach them during attempt to read old dump file. See for example discussion http://stackoverflow.com/questions/30459260/jacoco-sonarqube-incompatible-version-1007