I'd like to check the minimum test coverage level in the mvn verify step of my build. I followed the instructions on the webpage: https://github.com/scoverage/scoverage-maven-plugin#checking-minimum-test-coverage-level

This works fine, but it also causes our tests (and scala-fmt) to run twice, which is very annoying and time-consuming.

In scoverage/scoverage-maven-samples#2 you say it's better to split the call to maven into two separate ones, for example mvn clean verify -DskipTests and mvn scoverage:check, which also works I suppose, but is also very unsatisfying: team members will have to learn to use Maven in a non-standward way if they want to verify their work before submitting it to the CI server. (Either having to remember both incantations and having to remember to type both, or having to use a shell script and remembering not to use Maven directly.)

In the mean time, JaCoCo can do coverage level checking directly from mvn verify without running the tests twice, so our team members are very much used to only having to type mvn verify or mvn install to execute all of the checks that the CI server also executes.

Would it be possible to add this behavior to scoverage-maven-plugin as well? It would make Scala adoption on our team so much easier.