Tobias Roeser
Tobias Roeser
Looks like we lost `mill.runner.MillBuild` external module, which allowed us to get the meta build level count. * introduced at: https://github.com/com-lihaoyi/mill/pull/2719 * removed at: https://github.com/com-lihaoyi/mill/pull/3717 Usage: ```console > MILL_VERSION=0.12.0 mill...
Some Mill runtime values are useful to be used in buildfiles, e.g. `env` variables, `respositories`, various versions ... In most cases, those values need to be consumed via an `Task.Input`,...
TBD With the merge of https://github.com/com-lihaoyi/mill/pull/4524, source tasks could no longer depend on other tasks. Due to this change, the logic to calculate changes, especially in the `--watch` mode complicated,...
That way, modules can use these value, e.g. `CoursierModule` can default to the same `repositories`.
Currently the BSP compilation for Scala Modules combines the results of the `compile` and the `semanticDbData` tasks. This assumes, that `semanticDbData` is produced in addition to the compilation. Effectively, in...
I guess the reason is, we need to change the build under test, but `testCached` is not a command, so there isn't by default a no-op checker in place.
On Windows, environment variables don't need to be cases-sensitive, hence a simple lookup for a key might not be enough. For example the `scala.sys.env` map has a `withDefault` override that...
The idea is to fully explode the example project into a given (or default `Task.dest`) directory, so that the user or developer can just cd into that project and inspect...
Before https://github.com/com-lihaoyi/mill/pull/4969, sub-package discovery and usage needed to be enabled explicitly (with `import $packages._`). Now, they will be used when found, which seems convenient in most cases. But it also...