Imagine a following scenario:
How could this happen?
A trick is that targetPercentage, statementPercentage, methodPercentage and conditionalPercentage all are being compared against actual project metrics using a numerical precision equal to a number of fractional digits set in these properties. A standard value rounding is used (BigDecimal.ROUND_HALF_EVEN).
For instance, if project's total code coverage is 99.9% and maven-clover2-plugin has a folowing setting:
then the comparison is made using no fractional digits. Therefore, 99.9 is rounded to 100 and clover2:check passes the build.
Therefore, to reach exactly 100%, maven-clover2-plugin shall have:
(six digits is enough as project's coverage percentage metric is stored in float)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs