Tobias Roeser

> With mill version 0.11.12 - 0.12.0-RC2 the example project [mill-scalajs-experiment] compiles in IntelliJ IDEA 2024.2.3 (Ultimate Edition) by removing the scala-library from scala_js_SDK. > > mill -j 0 mill.idea.GenIdea/idea;...

Although I think IDEA is misbehaving, if this solves the issue, I can implement this specific logic.

FTR, the example works in `main` branch, which is 1ca8b97ec5b7e81768f9d96d5462af5414db25d3 ```console > git rev-parse HEAD 1ca8b97ec5b7e81768f9d96d5462af5414db25d3 > mill --version Mill Build Tool version 1.0.0-RC2 Java version: 17.0.14, vendor: Azul Systems,...

For versions since Mill 0.12.13, the file has another file extension: "exe". This is due to a newly introduced restriction in Maven Central. We are no longer allowed to use...

@alexarchambault Can you help out how we can specify the file extension for a dependency?

Assuming, we want a short notification like we have for `classifier` as in `mvn"com.lihaoyi:mill-dist:0.12.14;classifier=tests"`, what would be the best name for it, `type`? We already have support for `type` which...

+1 for switching over to _using directives_! * https://github.com/com-lihaoyi/mill/issues/3062

> > We should run through this PR, identify all such 2.13-compatible changes, and land them separately before the breaking Scala 3 changes > > you can include even more...

If we can't access the full path from ASM, we could make the generated filename more special, e.g. by always appending a `MillGenerated`, then we can detect and handle it...

We could cut a `3.0.0` instead. We entered a milestone-release phase for `3.0` to be open to binary incompatible changes. But it looks like none more are planned, so we...