Is there a way how to exclude scoverage.compile when running wildcard compile?

[davidak09]

Currently, running ./mill __.compile triggers compilation for all modules, including those generated by the Scoverage plugin. This significantly increases build time when a full coverage run isn't intended.

Steps to reproduce:

• Setup a Mill project with ScoverageModule.
• Run ./mill __.compile
• Observe that tasks like a.scoverage.compile are executed.

Mill Version: 1.0.6

[lefou]

You can use type filters to achieve that.

Here is an example (using on of my repos that use the Scoverage plugin).

> git remote -v 
origin  https://github.com/lefou/mill-integrationtest.git (fetch)

> mill resolve __.compile
integrationtest[0.10].compile
integrationtest[0.10].scoverage.compile
integrationtest[0.10].test.compile
integrationtest[0.11].compile
integrationtest[0.11].scoverage.compile
integrationtest[0.11].test.compile
integrationtest[0.9].compile
integrationtest[0.9].scoverage.compile
integrationtest[0.9].test.compile

> mill resolve __:^ScoverageData.compile
integrationtest[0.10].compile
integrationtest[0.10].test.compile
integrationtest[0.11].compile
integrationtest[0.11].test.compile
integrationtest[0.9].compile
integrationtest[0.9].test.compile

As you can see, with __:^ScoverageData.compile you can select all modules except ScoveragaData, which is the type of the inner scoverage module.

[davidak09]

Thanks for the answer! It's a good enough workaround. I guess there isn't like "reverted" approach, meaning to only include scoverage.compile when I want to, is there? Or something like command alias.

[lefou]

Not really, since ScoverageData is a full featured ScalaModule and you used the catch-all wildcard __.

In case you use a shared trait for all your modules, e.g. MyModule, you could instead use mill __:MyModule.compile.