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.
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
Include JaCoCo version in instrumentation/analysis exception messages #1217
Include JaCoCo version in instrumentation/analysis exception messages #1217
Changes from 2 commits
161deee
9e736bf
f9e49cf
6b76303
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@marchof this is indeed qualified version, i.e. in https://repo1.maven.org/maven2/org/jacoco/org.jacoco.core/0.8.7/org.jacoco.core-0.8.7.jar
So I'm wondering whether change of javadoc here implies that you expect(ed) to see
instead of
?
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.
Ups my bad. I was wrongly assuming we have the plain version here. From my point of view the plain version would be enough here. What do you think, can we change this to
project.version
?If we don't want to change this in this PR the qualified version is also good for me.
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.
Well I have mixed feelings:
Maybe not a big deal to change it, however strictly speaking it is part of our public API on it's own and a return value of Agent API
org.jacoco.agent.rt.IAgent.getVersion
, also it is shown byversion
command in CLI and always displayed in footer (right-bottom corner) of html reports.And on one side, since qualifier is build timestamp, maybe nice that people will see how old version they are using. On the other side, since their configuration files use unqualified version, presence of qualifier might be confusing.
We can introduce
VERSION_SHORT
by analogy withCOMMITID_SHORT
, but maybe this is an overkill.So let's keep it as is for now.
I'll add back word "Qualified" so that it can again remind us next time 😉
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.
@marchof BTW fun fact:
COMMITID_SHORT
is the first 7 digits ofCOMMITID
computed at runtime,RUNTIMEPACKAGE
is the last 7 digits ofCOMMITID
computed at build time😆
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.
@marchof hope people won't be faking this value in forks 😉
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.
Well ... 🤷♂️