Tobias Roeser
Tobias Roeser
Introduce a `BspExtension` trait, which holds a class name and it's potential ivy dependencies. Split up the various BSP server extensions and instantiate them independently. They are now concrete classes...
Currently, `mill inspect` only works for targets, but not for modules. For module, it just outputs an error message "inspect Cannot find default task to evaluate for module foo". Instead,...
Until version 0.11.0-M8 we had documentation for each released version. Then, @lihaoyi extended the documentation to include executable examples, which we also run as part of our integration test suite....
Which Mill version supports: * which JDK version runtime / target platfrom * which Scala versions * which Scala.js versions * which Scala Native versions See also https://github.com/scala/docs.scala-lang/pull/2909
## Curent Limitations Current `CompilationResult` is very specific for the zinc compiler. ```scala case class CompilationResult(analysisFile: os.Path, classes: PathRef) ``` It's hard to integrate other compilers easily into Mill: *...
Currently, we use the Mill launcher jar to compile the Mill project. To do that, we add it to the `unmanagedClasspath` of the `MillBUildModule`. Technically, this is correct. But in...
This come in handy to prepare some offline work. It's also useful when a target itself is able to watch it's inputs (like a Spring Boot or Vaadin app) but...
*Details later*