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
When running Mill from the CLI, it is sometimes desirable to sequentially run some tasks.
Some use cases:
Run a clean build
Run coverage reports after running tests
Do full compilation (instead of incremental compilation) to detect all cyclic dependencies with acyclic compiler plugin
Currently, for all these actions, we need to run Mill multiple times with different tasks. Although this is not big issue, it might be still more convenient to have dedicated support, since a single command is easier to communicate and also all those auxiliary output like out/mill-chrome-profile.json would be more expressive.
I propose the ++ separator for sequentially task dependencies as it nicely matches the already supported + separator to request multiple tasks in parallel.
It would first run clean, afterwards it would run all jar and testCached tasks in parallel. And finally, when these are finished, it will generate a Scoverage console report collecting all the test coverage data.
Example for 3:
mill clean __.compile ++ __.compile
It first drops all compile task caches, then runs all compile tasks including its prerequisites.
The text was updated successfully, but these errors were encountered:
When running Mill from the CLI, it is sometimes desirable to sequentially run some tasks.
Some use cases:
acyclic
compiler pluginCurrently, for all these actions, we need to run Mill multiple times with different tasks. Although this is not big issue, it might be still more convenient to have dedicated support, since a single command is easier to communicate and also all those auxiliary output like
out/mill-chrome-profile.json
would be more expressive.I propose the
++
separator for sequentially task dependencies as it nicely matches the already supported+
separator to request multiple tasks in parallel.Example for 1 + 2:
It would first run clean, afterwards it would run all
jar
andtestCached
tasks in parallel. And finally, when these are finished, it will generate a Scoverage console report collecting all the test coverage data.Example for 3:
It first drops all
compile
task caches, then runs allcompile
tasks including its prerequisites.The text was updated successfully, but these errors were encountered: