Tobias Roeser

There is another option. You could prepare a trait which copies/shares everything with the `outer` module but still allows punctual overriding of tasks like `androidIsDebug`. That way, you could avoid...

"Task groups" is probably not a good name, since we already use the term "group" in `GroupExecution`, where a groups consists of all (anonymous) tasks representing a single terminal.

I mean, it also doesn't work for `Seq(1,2,3).map(n => test("testing-${n}") { ... )` or `.foreach`.

From a quick glance, this approach looks good to me. I'm not sure what you refer to with "shared base trait approach". In general, I think the variant-sub-modules should be...

It you see these warning only sometimes, chances are, these come from a freshly starting Mill daemon process, which is stopping itself after some idle-time. To customize the flags of...

The workaround is to add a second "hidden" `@main`-method. ```scala package build import mill.* object foo extends Module { def cmd1(args: String*) = Task.Command(exclusive = true) { mainargs.Parser(this).runOrThrow( args =...

Instead, we want something like this: ```scala package build import mill.* object foo extends Module { def cmd1(args: String*) = Task.Command(exclusive = true) { mainargs.Parser(this).runOrThrow( args = args, allowPositional =...