You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,14 @@ turn it back off when you're done running reports, use the `coverageOff` command
54
54
55
55
Sample project with scoverage in both sbt and maven - [the scoverage samples project](https://github.com/scoverage/sbt-scoverage-samples).
56
56
57
+
## Notes on upgrading to version 1.6.0
58
+
59
+
*`coverageAggregate` aggregates raw coverage data, not coverage xml reports for modules.
60
+
There is no requirement to generate individual coverage reports for modules (`coverageReport`)
61
+
before generating aggregated report (`coverageAggregate`).
62
+
63
+
If only aggregated report is required, not executing `coverageReport` can reduce the build time significantly.
64
+
57
65
## Notes on upgrading to version 1.3.0
58
66
59
67
* The object containing the keys has changed from nested to top level so you might need to adjust the import. It's also an auto plugin now, so you might not need the import at all.
0 commit comments