-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add internal tool that shows difference between two JaCoCo XML reports #811
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
base: master
Are you sure you want to change the base?
Conversation
@Godin I'm not sure whether this more like a tool than a educational example about our API usage. Have you considered adding this to the CLI instead? |
@marchof I thought about this option - as it is now, it fits well into examples, because
|
public InputSource resolveEntity(final String publicId, | ||
final String systemId) { | ||
if (publicId.startsWith("-//JACOCO//DTD Report")) { | ||
return new InputSource(new StringReader("")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an example and should follow best practices:
- check for exact DTD version to ensure compatibility
- Supply actual DTD otherwise this will fail when we merge Do not print default zero values of attributes in XML report #813
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describ 8000 e this comment to others. Learn more.
Sorry, my bad: I overlooked that parseAsOptionalInt()
already checks for null
values.
c97aecf
to
dbd5f99
Compare
I used this little utility to check changes in filters on a real projects. And would like to add it as an example.