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
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -112,16 +112,22 @@ and using the scoverage scalac plugin (`compileScoverageScala`).
112
112
113
113
In cases where you only wish to generate reports / validate coverage, but are not interested in publishing the code,
114
114
it is possible to only compile the code with the scoverage scalac plugin, thus reducing build times significantly.
115
-
In order to do so, simply add the arguments `-x compileScala` to the gradle execution.
116
-
For example: `gradle reportScoverage -x compileScala`.
115
+
In order to do so, simply add the arguments `-PscoverageCompileOnly` to the gradle execution.
116
+
For example: `gradle reportScoverage -PscoverageCompileOnly`.
117
117
118
+
Note that this mode is incompatible with parallel builds in multi-module projects.
118
119
119
120
### Compatibility with Consistent Versions Plugin
120
121
121
122
In order for the plugin to work alongside [Palantir's consistent versions plugin](https://github.com/palantir/gradle-consistent-versions),
122
123
the Scala version must be manually configured (via `scoverageScalaVersion`); otherwise, the plugin will attempt to
123
124
resolve the compilation classpath, which is prohibited by the versions plugin.
124
125
126
+
Migration to 6.1.1
127
+
----------------
128
+
129
+
* Running without normal compilation is now made with `-PscoverageCompileOnly` instead of `-x compileScala`.
0 commit comments