-
```scala
// build.sc
import mill._, scalalib._
object root extends RootModule with ScalaModule {
def scalaVersion = "3.3.0"
}
```
**Only when using BSP**, Metals output gives this output:…
-
Hi!
When trying to update the version of Upickle being used in the app, I'm running into a linkage error: a `java.lang.NoSuchMethodError`.
The problem appears to be caused by the Mill launcher p…
-
I've been having issues running `mill cli[2.12.18].mostly-static-image.nativeImage` on the coursier codebase and I went down a rabbit hole of why this wasn't working. It looks like with some of the ne…
-
I encountered this when writing a Mill plugin. When creating an `ExternalModule` you'll have code that looks like this:
```scala
import mill._
import mill.define.Command
import mill.define.Exter…
-
**Is your feature request related to a problem? Please describe.**
Currently, Deequ only gets published for a small subset of combinations of Scala version ✖️ Spark version.
People are running into…
-
There should be some way to declare the minimal required mill version to be used.
If you currently start the build with the wrong version of mill, you might get strange compile errors or unexpected…
lefou updated
5 months ago
-
it's a wonderful plugin. will be great if we have something similar for mill (mill-ide-settings) :)
-
The goal of this ticket is to move Mill from Scala 2.13 to Scala 3.
Most of Mill's code should be easily portable with minimal changes (e.g. syntax tweaks), but there are three major areas which ma…
-
I'm checking compilation locally to reduce CI job runs (that's a [different story](https://github.com/com-lihaoyi/mill/pull/1933) though).
When I re-run a compilation (`mill contrib.flyway.compile`…
-
Export tested with Win OpenSCAD 2015.03-2 and Win OpenSCAD 2017.01.20
Import tested with illustrator, inkscape, 3D Studio, Vetrics Aspire
A Cycle with r 1.5mm is after export x=3mm, y=2,994mm
…