Tobias Roeser
Tobias Roeser
Otherwise, it's hard to know which options are available. E.g. The page https://mill-build.org/mill/migrating/auto-migrating.html shows an example with a `--jvm-id` option, but when I try to use it, it fails with:...
Mill is handling environment variables inconsistently. Most env vars have a higher priority that file-based configurations. E.g. We allow to change the Mill version with `MILL_VERSION`, even when there is...
Currently, only one very rudimentary ordering rule is supported by the planner/executor: _Exclusive tasks run last_ This is rather a low complexity implementation to support exclusive tasks. While there is...
* Mill 0.12.16 * ammonite 3.0.2 * classgraph 4.8.181 * coursier 2.1.25-M18 * coursier-interface 1.0.29-M2 * commons-io 2.20.0 * semanticdb-java 0.11.1 * jarjar-abrams-core 1.15.0 * logback-classic 1.5.18
Currently, those args are listed explicitly in the `.bsp/mill-bsp.json`.
For example, the whole `mill.constants` package is not included in the API documentation.
Currently, the template mechanisms to render the documentation text is not well documented, rather hidden and not intuitive. IIUC, it re-uses some text found in an equally named file under...
It looks like, we currently can't control the default repositories via a YAML header. But this is, what most users want. E.g. to use a Scala 3.8 nighly release, one...
Often, the easiest way to use `inspect` for nested tasks is to prepend it with `__.`. ```console > mill inspect __.publishM2Local contrib.artifactory.publishM2Local(PublishModule.scala:435) Publish artifacts to a local Maven repository. @param...
Currently, the task query syntax (https://mill-build.org/mill/cli/query-syntax.html) is based on types. Since modules in Mill are Scala `object`s, each module has it's own type, so it is already possible to exclude...