Tobias Roeser

My specific use case is the need to disable some specific test in CI (https://github.com/com-lihaoyi/mill/pull/5921).

Merged in latest changes from `main` branch, fixed conflicts and added a `OptMap` type alias to make working with maps containing config data more convenient.

Are these apps written from scratch or did you copy them from somewhere else? If they are copies, you should add a comment where they come from, which version you...

As a workaround, one can use ```console > mill show foo.jar \\+ bar.jar [1/1] show { "foo.jar": "ref:v0:b0782d30:/tmp/mill1/out/foo/jar.dest/out.jar", "bar.jar": "ref:v0:e695f764:/tmp/mill1/out/bar/jar.dest/out.jar" } [1/1] ============================== show foo.jar \+ bar.jar ============================== ```

The question is "when" these properties files should be read? The `JavaModule.resources` task does contain runtime-resources. If you need resources at compile-time, you need to use `JavaModule.compileResources` (associated to `compile-resources`...

@vaslabs Probably related: https://github.com/com-lihaoyi/mill/pull/6168#issuecomment-3528129611 (If this involves annotation processors)

Ok. Please make sure your PR answers the question where the need to use `KotlinMavenModule` comes from. Is it required due to technical limitations, or just because the source directories...

I think we should ultimately try to fix the underlying problem. Mill allows users to configure all inputs, so we should explicitly state modules, that don't support that or require...

This is only relevant for Metals, which requires semanticDb, but IntelliJ IDEA does not. Our BSP implementation should already be able to decide whether `compile` or `semanticDbDataDetailed` is needed.

I meant, our BSP server implementation is already aware, whether we need semanticDb data or not. We have that info in `MillBuildServer.SessionInfo.clientWantsSemanticDb` and it should be respected in the compilation...