In-process tests live in the .test sub-modules of the various Mill modules. These range from tiny unit tests, to larger integration tests that instantiate a TestUtil.BaseModule in-process and a TestEvaluator to evaluate tasks on it.

Most "core" tests live in main.__test; these should run almost instantly, and cover most of Mill’s functionality that is not specific to Scala/Scala.js/etc.. Tests specific to Scala/Scala.js/Scala-Native live in scalalib.test/scalajslib.test/scalanativelib.test respectively, and take a lot longer to run because running them involves actually compiling Scala code.

The various contrib modules also have tests in this style, e.g. contrib.buildinfo.test

Note that the in-memory tests compile the BaseModule together with the test suite, and do not exercise the Mill script-file bootstrapping, transformation, and compilation process.

example.__.local and integration.__.local tests run Mill end-to-end in a subprocess, but without the expensive/slow steps of packaging the core packages into an assembly jar and publishing the remaining packages to ~/.ivy2/local. You can reproduce these tests manually using ./mill dev.run <test-folder-path> <command>.

example tests are written in a single build.sc file, with the test commands written in a comment with a bash-like syntax together with the build code and comments that explain the example. These serve three purposes:

1. Basic smoke-tests to make sure the functionality works at all, without covering every edge case

2. User-facing documentation, with the test cases, test commands, and explanatory comments included in the Mill documentation site

3. Example repositories, that Mill users can download to bootstrap their own projects

The integration tests are similar to example tests and share most of their test infrastructure, but with differences:

1. integration tests are meant to test features more thoroughly then example tests, covering more and deeper edge cases even at the expense of readability

2. integration tests are written using a Scala test suite extending IntegrationTestSuite, giving more flexibility at the expense of readability

You can reproduce any of the tests manually using dev.run, e.g.

Automated Test

Manual Test

Manual Test using Launcher Script

example.__.server, integration.__.server, example.__.fork and integration.__.fork cover the same test cases as the .local tests described above, but they perform packaging of the Mill core modules into an assembly jar, and publish the remaining modules to ~/.ivy2/local. This results in a more realistic test environment, but at the cost of taking tens-of-seconds more to run a test after making a code change.

You can reproduce these tests manually using dev.assembly:

There are two flavors of these tests:

1. .server test run the test cases with the default configuration, so consecutive commands run in the same long-lived background server process

2. .fork test run the test cases with --no-server, meaning each command runs in a newly spawned Mill process

In general you should spend most of your time working with the .local version of the example and integration tests to save time, and only run .fork or .server once .local is passing.

To test bootstrapping of Mill’s own Mill build using a version of Mill built from your checkout, you can run

This creates a standalone assembly at target/mill-release you can use, which references jars published locally in your ~/.ivy2/local cache, and applies any necessary patches to build.sc to deal with changes in Mill between the version specified in .config/mill-version that is normally used to build Mill and the HEAD version your assembly was created from. You can then use this standalone assembly to build & re-build your current Mill checkout without worrying about stomping over compiled code that the assembly is using.

This assembly is design to work on bash, bash-like shells and Windows Cmd. If you have another default shell like zsh or fish, you probably need to invoke it with sh ~/mill-release or prepend the file with a proper shebang.

If you want to install into a different location or a different Ivy repository, you can set it’s optional parameters

In case of troubles with caching and/or incremental compilation, you can always restart from scratch removing the out directory:

• runner, main.*, scalalib, scalajslib, scalanativelib.

These are general lightweight and dependency-free: mostly configuration & wiring of a Mill build and without the heavy lifting.

Heavy lifting is delegated to the worker modules (described below), which the core modules resolve from Maven Central (or from the local filesystem in dev) and load into isolated classloaders.

• scalalib.worker, scalajslib.worker[0.6], scalajslib.worker[1.0]

These modules are where the heavy-lifting happens, and include heavy dependencies like the Scala compiler, Scala.js optimizer, etc.. Rather than being bundled in the main assembly & classpath, these are resolved separately from Maven Central (or from the local filesystem in dev) and kept in isolated classloaders.

This allows a single Mill build to use multiple versions of e.g. the Scala.js optimizer without classpath conflicts.

• contrib/bloop/, contrib/flyway/, contrib/scoverage/, etc.

These are modules that help integrate Mill with the wide variety of different tools and utilities available in the JVM ecosystem.

These modules are not as stringently reviewed as the main Mill core/worker codebase, and are primarily maintained by their individual contributors. These are maintained as part of the primary Mill Github repo for easy testing/updating as the core Mill APIs evolve, ensuring that they are always tested and passing against the corresponding version of Mill.

• Changes to the main branch need a pull request. Exceptions are preparation commits for releases, which are meant to be pushed with tags in one go

• Merged pull request (and closed issues) need to be assigned to a Milestone

• Pull requests are typically merged via "Squash and merge", so we get a linear and useful history

• Larger pull request, where it makes sense to keep single commits, or with multiple authors may be committed via merge commits.

• The title should be meaningful and may contain the pull request number in parentheses (typically automatically generated on GitHub)

• The description should contain additional required details, which typically reflect the content of the first PR comment

• A full link to the pull request should be added via a line: Pull request: <link>

• If the PR has multiple authors but is merged as merge commit, those authors should be included via a line for each co-author: Co-authored-by: <author>

• If the message contains links to other issues or pull requests, you should use full URLs to reference them

This release is binary incompatible to 0.11.0-M7.

Changes since 0.11.0-M7:

• Added an example/ folder in the Mill repo, containing common build setups demonstrating Mill features with explanations of how each feature works

• Pre-compiled Scala incremental compiler interface #2424, to speed up clean builds

• Add some helpers to simplify cross-version/cross-platform modules {#2406}[com-lihaoyi#2406]

• You can now override T{…​} Targets with T.source or T.sources, and vice versa #2402

• Removed the Ammonite script runner dependency used to evaluate build.sc files and instead compile them using Mill #2377

• Add TestModule.ZioTest {#2432}[com-lihaoyi#2432]

• Caching fixes for external modules #2419

• Overhaul of the Mill BuildInfo plugin, moving the key-value into resources to avoid needing to re-compile your module when the values change, adding JavaModule support, and allowing Javadoc/Scaladoc comments to be associated with the generated BuildInfo constants #2425

• Global Configuration via ~/.mill/ammonite/predefScript.sc is no longer supported in this version. If that breaks your workflow, please report and tell us your use case so we can provide sufficient replacement or support for your use case before Mill 0.11.

• Overhaul of the documentation. Created many executable example projects which are included in the documentation and run/tested on CI

• Change cross module definitions to be traits instead of classes, for greater regularity and less builerplate at call sites. This change requires slight modification to existing build scripts that define cross modules.

For details refer to milestone 0.11.0-M8 and the list of commits.

This release is binary incompatible to 0.11.0-M6.

Changes since 0.11.0-M6:

• Introduced automatic PathRef validation for cached targets; default-enabled it for CoursierModule.resolveDeps and various resolvedIvyDeps targets

• bsp: Update Protocol version to 2.1.0-M4

• bsp: Support new mainClasses field in run and test environments

• bsp: Fixed handling of Mill plugins and other improvements

• scalanativelib: new nativeDump setting in ScalaNativeModule

• contrib.twirllib: Use newer scala-parser-combinators version when used with Scala 3

• contrib.scalapblib: Added new flag to search for proto files in dependencies

• Various refactorings to improve binary compatibility

• Updated dependencies: Ammonite 3.0.0-M0-5 coursier 2.1.0, scala native tools 0.4.12, semanticdb 4.7.6, trees 4.7.6, upickle 3.0.0

• DX improvements

For details refer to milestone 0.11.0-M7 and the list of commits.

This release is binary incompatible to 0.11.0-M5.

Changes since 0.11.0-M5:

• main: Re-added missing --color and predef cli arguments.

For details refer to milestone 0.11.0-M6 and the list of commits.

This release is binary incompatible to 0.11.0-M4.

Changes since 0.11.0-M4:

• Cross is no longer adding the cross parameters to the millSourcePath.

  You should review your cross modules setups to avoid build issues like incorrect source paths or missing files. CrossScalaModule is not affected by this change.

• API refactorings: PathRef, moved JarManifest to mill.main

• No longer inherit the Ammonite CLI config

• scalalib: Fixed loosing customized mapDependencies when ScalaModule get mixed in after

• scalalib: New TestModule.Weaver

• scalajslib: New JsEnvConfig.Selenium

• testrunner: Fixed concurrency issue with test event reporting

• Updated dependencies: ammonite 3.0.0-M0-3, coursier 2.1.0-RC6, jarajar-abrams-core 1.8.2, lambdatest 0.8.0, log4j-core 2.20.0, os-lib 0.9.1, scoverage 2.0.8, semanticdb-scalac 4.7.5, trees 4.7.5

• Documentation updates

For details refer to milestone 0.11.0-M5 and the list of commits.

This release is binary incompatible to 0.11.0-M3.

Changes since 0.11.0-M3:

• scalalib: New configuration target zincReportCachedProblems which, when true, enables reporting of all found problems, even for files which were not re-compiled

• scalalib: Improved SemanticDB support for Java and Scala

• scalalib: Mitigate another coursier download issue

• scalajslib: Fetch more tooling dependencies in prepareOffline

• scalanativelib: Fetch more tooling dependencies in prepareOffline

• scalanativelib: Updated tools to version 0.4.10

• bsp: Improved support for the mill-build module which should improve the editing experience for build.sc and other build files

• Cleanups and internal improvements

• Updated dependencies: Ammonite 3.0.0-M0-1, junixsocket 2.6.2, semanticdb-java 0.8.13, upickle 3.0.0-M2

For details refer to milestone 0.11.0-M4 and the list of commits.

This release is binary incompatible to 0.11.0-M2.

Changes since 0.11.0-M2:

• Slightly changed the out/ folder layout for overridden and private tasks. Instead of foo.overridden we now use a foo.super path to hold the metadata and scratch files.

• Fixed the caching for private targets with same name but defined in different super traits.

• Fixed non-functional clean command when used with arguments denoting modules.

• scalalib: Fixed GenIdea issues on Windows, when the build uses plugins or additional libraries.

• scalajslib: ScalaJSModule.ScalaJSModuleTests now extends ScalaModule.ScalaModuleTests which improves consistency, better default values and compatibility with other modules like ScoverageModule.

• scalanativelib: ScalaNativeModule.ScalaNativeModuleTests now extends ScalaModule.ScalaModuleTests which improves consistency, better default values and compatibility with other modules.

• contrib.gitlab: Improved error handling for token lookup and documentation.

• Updated dependencies: coursier 2.1.0-RC5, jna 5.13.0, semanticdb-scala 4.7.3, trees 4.7.3

• Documentation improvements

For details refer to milestone 0.11.0-M3 and the list of commits.

This release is binary incompatible to 0.11.0-M1.

Changes since 0.11.0-M1:

• Splitted BSP module into mill.bsp and mill.bsp.worker and removed various dependencies (guava, bsp4j, xtends, lsp4j, …​) from Mill API

• scalalib: Added support to generate semanticdb data for Java source files

• scalajslib: Added support for scalaJSOutputPattern

• scalajslib: Added suport for scalaJSSourceMap

• scalajslib: Dropped support for Scala.js 0.6

• Updated dependencies: ammonite 2.5.6, coursier 2.1.0-RC4, semanticdb 4.7.1, requests 0.8.0, scalafmt 3.6.1, trees 4.7.1, upickle 3.0.0-M1, utest 0.8.1

• Various internal cleanups and improvements

• Documentation improvements

For details refer to milestone 0.11.0-M2 and the list of commits.

This release is binary incompatible to 0.10.10.

Changes since 0.10.10:

• Greatly improved dependency resolution between modules, making it possible to mix Java and Scala modules

• main: Restrict Cross parameter to be of type Module

• scalalib: Performance improvements in Zinc worker module

• scalalib: Resources are no longer added to compileClasspath.

• scalalib: Added new compileResources which will end up in compileClasspath

• scalalib: Consolidated artifact and platform suffix handling

• scalajslib : Performance improvements in worker module

• scalanativelib : Performance improvements in worker module

• Updated dependencies: coursier 2.1.0-RC3, os-lib 0.9, scala 2.12.17, trees 4.7.0

• Removed lots of deprecated API

• Various internal cleanups and improvements

For details refer to milestone 0.11.0-M1 and the list of commits.

Changes since 0.10.11:

• scalalib: Mitigate another coursier download issue (backported from 0.11.0-M4)

• testrunner: Fixed a concurrency issue with test event reporting (backported from 0.11.0-M5)

• scalajslib: Deprecated fastOpt and fullOpt

• Updated dependencies: coursier 2.1.0, jarjar-abrams 1.8.2, jna 5.13.0, junixsocket 2.6.2, log4j-core 2.20.0, scalafmt-dynamic 3.6.1, trees 4.7.6

For details refer to milestone 0.10.12 and the list of commits.

Changes since 0.10.10:

• Fixed non-functional clean command when used with arguments denoting modules.

• scalalib: Fixed GenIdea issues on Windows, when the build uses plugins or additional libraries.

• scalajslib: Performance improvements in worker module

• scalajslib: Pass more settings from ScalaJSModule to its Tests

  If you have issues after the update (like org.scalajs.jsenv.UnsupportedInputException, com-lihaoyi#2300), check your settings in the test modules for consistency.

• Some internal improvements backported from 0.11.0-M3

For details refer to milestone 0.10.11 and the list of commits.

After this release, the main branch is open for development of the next major version of Mill, which is probably 0.11. Further maintenance work will happen in the 0.10.x branch.

Changes since 0.10.9:

• Lots of documentation improvements, additions and restructurings

• core: Fixed some rare issues with reading the .mill-jvm-opts file

• core: We made slight adaptions to the T.dest location of target defined in included files, to fix potential colliding cache locations

• scalalib: JAR archives created by Mill now by default contain directory entries

• scalalib: Updated zinc to 1.8.0

• scalajslib: Added support for more JsEnv providers

  If you get some issues (like connect ECONNREFUSED, com-lihaoyi#2204) after the update, review your settings for JsEnv providers.

• scalanativelib: Support for incremental compilation since Scala Native 0.4.9

• contrib.testng: The TestNG library is no longer provided transitively; you need to provide it explicitly

• contrib.bloop: Fixed re-generation of bloop config dir; previously, it could happen, that there where no config files at all

• BSP: implement buildTarget/OutputPaths request

• Various version bumps and internal improvements

For details refer to milestone 0.10.10 and the list of commits.

Changes since 0.10.8:

• Hardened Maven and Ivy artifact handling to prevent path-traversal attacks (see CVE-2022-37866), also updated coursier dependency to a non-vulnerable version

• Decoupled mill-moduledefs module into a separate project, to better suite compiler plugin packaging and improve support for various Scala versions

• Applied more workarounds to coursier concurrency issues to make parallel builds more robust

• Added support for newer Scala versions in GenIdea (2.2 and 2.3)

• Fixed an issue where PublishModule dropped module dependencies when mixed-in after other trait which overrode moduleDeps

• new JMH contrib plugin

• Lots of internal improvements and dependency updates

For details refer to milestone 0.10.9 and the list of commits.

Changes since 0.10.7:

• Improvements for better Scala 3.2 support

• Fixed non-working default commands in cross modules

• CoursierModule: mitigate more download failure situations (e.g. checksum failures)

• PublishModule: properly show gpg output in server mode

• BSP: Better compiler message handling (logMessage instead of showMessage) and support for diagnostic code

• ScoverageModule: Support for Scoverage 2.x

• New contrib module GitlabPublishModule

• Various internal improvements and version bumps

• Documentation improvements

For details refer to milestone 0.10.8 and the list of commits.

Changes since 0.10.6:

• Don’t print unwanted debug messages from zinc

For details refer to milestone 0.10.7 and the list of commits.

Changes since 0.10.5:

• PathRefs sigs are now more reproducible and independent of the used filesystem

• JavaModule can now use a non-local Java Compiler to support all options

• Logger: new debugEnabled to detect whether debug logging is enabled

• New testkit module, to use TestEvaluator in external projects

• Fixed reading of .mill-jvm-opts in server mode

• BSP: Automatic SemanticDB enablement to improve Metals support

• mill.twirllib.TwirlModule - new mandatory target twirlScalaVersion to configure the Scala version used by Twirl compiler, and support for newer versions

• Lots of documentation updates and additions

• Upgraded to Zinc 1.7.1 and various other dependency updates

For details refer to milestone 0.10.6 and the list of commits.

Changes since 0.10.4:

• New init command, to create new Mill projects from Gitter8 (g8) templates

• PathRef now gracefully ignores socket files. This also fixes an annoying issue when Mill was previously ran in a source directory.

• Fixed a bug with using mill --repl without any further arguments, which was introduced in Mill 0.10.2 and prevented proper no-server mode

• Fixed the visualize command which wasn’t working on some newer JREs

• Improved Mill server support for Windows 11 and some Windows Server versions

• ScalaModule / ZincWorkerModule: Fixed incremental compilation issue with JRE 17 (and probably others)

• TestModule now better supports JUnit5 test suites

• ScalaJsModule: internal improvements to the stability of the Scala.js linker

• ScalaNativeModule: Added support for nativeEmbedResources

• BSP: improved handling of the mill-build module when the BSP client is IntelliJ IDEA

• Documentation updates and link fixes

• Various dependency updates

For details refer to milestone 0.10.5 and the list of commits.

Changes since 0.10.3:

• Switched from ipcsocket to junixsocket library to enhance the robustness of Mill client server communication. This should greatly improve the user experience on Windows.

• Internal improvements and better support of GraalVM

• The Mill Documentation site has now built-in search functionality

• ScalaJsModule: New targets fastLinkJS and fullLinkJS and deprecated fastOpt and fullOpt

• ScalaJsModule: Support for ModuleSplitStyle

• BSP: Updated to protocol version 2.1.0-M1, added support for test framework names and support for the JVM extension

• GenIdea: More consistent ordering of libraries and dependent modules and support for Scala 3.1 language level

• Bloop: Added support for runtime dependencies

• Enhanced test suite to cover Mill client server scenarios

• Various dependency updates

For details refer to milestone 0.10.4 and the list of commits.

Changes since 0.10.2:

• Fixed import $file for files with hyphens and other symbols in its name

• Fixed an issues with truncated output just before Mill finishes

• Mill commands now support arguments of type Task[T], which can improve writing re-usable commands, especially, they can be called from other tasks more easily

• JavaModule: Improved correctness and performance of compileClasspath and bspCompileClasspath targets. This fixes an issue with BSP for large projects. Also, compile-time dependencies no longer sneak into the classpath transitively.

• JavaModule: Added docJarUseArgsFile target and fix issue with Windows command length restrictions in docJar

• BSP and Bloop: Better detect foreign modules

• Various internal API refinements and improvements

• Reorganized integration test suite and build setup

For details refer to milestone 0.10.3 and the list of commits.

Changes since 0.10.1:

• Mill workers can now implement AutoCloseable to properly free resources

• ScalaModule: Fixed repl start

• CoursierModule: Fixed concurrent download issues with coursier (we detect and retry)

• MainModule: Fixed potential match error with show and showNamed

• Restructured contrib module documentation

• Internal improvements

For details refer to milestone 0.10.2 and the list of commits.

Changes since 0.10.0:

• MillClienMain can now act as universal main to start mill with or without a server process

• Improved show command that always returns valid JSON

• Added showNamed command that includes the task names in the output

• Implemented more granular cache invalidation which keeps more caches intact when you split your build setup over multiple .sc files with import $file.

• The local .mill-jvm-opts file is no longer restricted to -X options

• CoursierModule: Added coursierCacheCustomizer to support a FileCache customizers

• JavaModule: the docJar target no longer includes hidden files

• ScalaModule: Updated to latest zinc version

• ScalaModule: Reworked scalac plugins handling for the better and to support Scala 3

• ScalaNativeModule: fixed Dep.withDottyCompat behavior

• ScalaJSModule: support for linking multiple modules

• ScalafmtModule: Support for newer Scalafmt versions

• Tool chain: Update to Mill 0.10.0

• Tool chain: we no longer create files outside the mill project directory (e.g. ~/mill-release is now under target/mill-release)

• Various dependency updates

• Lots of internal improvements

For details refer to milestone 0.10.1 and the list of commits.

Changes since 0.10.0-M5:

• Changed structure of out directory, out/foo/dest is now out/foo.dest

• Fixed issues with loading of predef scripts

• --watch now supports manual re-runs by pressing enter

• Improved subprocess handling

• Published poms can now contain properties and versionScheme information

• Improved Scala.js support, including more target configuration options and support for Node 17

• Improved Scala Native for version > 0.4.2 and support Scala 3

• Internal improvements, fixes and dependency version updates

For details refer to milestone 0.10.0 and the list of commits.

This release breaks binary compatibility for external plugins.

Changes since 0.10.0-M4:

• Fixed Log4Shell security vulnerability in ZincWorkerModule (CVE-2021-44228)

• Factored out the testrunner into a new module, which also fixes some potential classloader issues when executing tests (e.g. with JNA)

• Removed the limitation of max 22 inputs for tasks

• --watched commands can now re-run when pressing enter-key

• task and arguments of commands can now have hyphens in their name

• Reworked and decluttered the out-folder structure

• prepareOffline now has a all flag to control if all or only some dependency should be prefetched

• Made caching more effective for targets overridden in stackable-traits

• Further BSP improvements, esp. for Metals and Scala 3

• Lots of other internal improvements and fixes

• Various dependency updates

For details refer to milestone 0.10.0-M5 and the list of commits.

Changes since 0.10.0-M3:

• BSP support rework and overhaul of built-in BSP server

• GenIdea: failures when inspecting and resolving the build are not properly reported

• Coursier: we now implemented a workaround to tackle concurrent downloads issues

• New + separator to provide multiple targets (with parameters) via cmdline

• New --import cmdline option to run ad-hoc plugins without editing of build.sc

• New T.ctx().workspace API to access the project root directory

• Various internal improvements and bug fixes

• Various refactorings and cleanups

For details refer to milestone 0.10.0-M4 and the list of commits.

This is a milestone release. This release breaks binary compatibility for external plugins build for mill 0.9.x. The API is suspected to change before a 0.10.0 releae.

Changes since 0.10.0-M2:

• ScalaModule with PublishModule: the scala-library artifact is now always part of the dependencies in published `pom.xml`s and `ivy.xml`s

• New JavaModule.mandatoryIvyDeps target to provide essential dependencies like scala-library without forcing the user to call super.ivyDeps

• ScalaJSModule.scalaLibraryIvyDeps no longer contains the scala-js-library, but only the scala-library; if you need that, use ScalaJSModule.mandatoryIvyDeps instead.

• import $ivy support $MILL_BIN_PLATFORM variable and a new sort notations for external plugins

• We fixed and enabled lots of tests to run on Windows

• Some generic targets like plan or path now also return their output

• GenIdea: improved support for Scala 3 projects *

For details refer to milestone 0.10.0-M3 and the list of commits.

This is a early milestone release. This release breaks binary compatibility for external plugins build for mill 0.9.x. The API is suspected to change before a 0.10.0 releae.

Changes since 0.9.9:

• Removed deprecated API

• ScalaModule: added mandatoryScalacOptions to avoid the common issue that users forget to include mandatory options when defining their own.

• Renamed toolsClasspath targets found in various modules to avoid hard to resolve clashes when mixing traits

• Fixed and improved our test suite on Windows

• Various fixes and improvements

• Various dependency updates

For details refer to milestone 0.10.0-M2 and the list of commits.

• fixed parsing of command parameters in show command

• zinc worker: Updated log4j2 to 2.17.1

For details refer to milestone 0.9.12 and the list of commits.

• zinc worker: Updated log4j2 to 2.16.0 to fix Log4Shell (CVE-2021-44228) vulnerability

For details refer to milestone 0.9.11 and the list of commits.

• Some feature backports from mill 0.10

• New + separator to provide multiple targets (with parameters) via cmdline

• New --import cmdline option to run ad-hoc plugins without editing of build.sc

• import $ivy support $MILL_BIN_PLATFORM variable and a new sort notations for external plugins

For details refer to milestone 0.9.10 and the list of commits.

Changes since 0.9.8:

• BSP: Fixed/improved source item for root project

• Bloop: Prevent compilation during bloop config generation

• GenIdea: Fix content path of root project (mill-build)

• Various version bumps

For details refer to milestone 0.9.9 and the list of commits.

Changes since 0.9.7:

• Fixed some potential binary incompatibilities with external plugins (builds against older os-lib versions)

• Fixed location and configuration of mills home path (used for caching of build scripts)

• Properly close jar resources - should fix issues in assembly, esp. on Windows where open resources are locked

• BSP: Repaired mills BSP server

• playlib: Fixed issues with the play-contrib module and added support for Play 2.8

• GenIdea: changed dir for generated mill modules to .idea/mill_modules

• Various version bumps, including Scala 2.13.5

For details refer to milestone 0.9.8 and the list of commits.

Changes since 0.9.6:

• ScalaModule: Support for Scala 3

• CoursierModule: Support customized dependency resolution (needed to work with ScalaFX)

• TestModule: Added new testFramework target and only support one test framework. Deprecated testFrameworks targets.

• TestModule: Added new convenience traits to configure popular test frameworks, e.g. TestModule.Junit4, TestModule.ScalaTest, TestModule.Utest and many more

• Bloop: Added support for foreign modules

• Better support for Windows environments

• Various internal improvements, cleanups, and deprecations

• Various dependencies updates

• Removed tut contrib module because of unmaintained/archived upstream dependency

For details refer to milestone 0.9.7 and the list of commits.

The mill project home and repository has been moved to https://github.com/com-lihaoyi/mill.

• repl and console targets now support forkArgs and forkEnv

• Support for Scala 3 release candidates and new Scaladoc 3 tool

• Support for Scala.js on Scala 3

• Scala Native improvements

• Test runner now uses an args file to support running tests on Windows

• GenIdea: better supports source jars, full config contributions and provided/runtime dependencies

• Various dependency updates

• Documentation site reworked to support multiple release versions

• Improved CI setup to better test mill on Windows

For details refer to milestone 0.9.6 and the list of commits.

• Updated zinc to 1.4.4

• Support for Scala Native 0.4.0

• Support for Scala.js ESModule (including Bloop support)

• Inner Tests traits in modules like JavaModule, ScalaModule and others now have unique names (JavaModuleTests, ScalaModuleTests, etc), to allow for easier customization

• Various version bumps of dependencies

• CI now runs all tests, it did miss some before

For details refer to milestone 0.9.5 and the list of commits.

• Implemented more BSP protocol commands and fixed some glitches with IntelliJ

• Stabilized CI builds

• Various fixes and improvements

• Various version bumps

For details refer to milestone 0.9.4 and the list of commits.

(We also tagged 0.9.0, 0.9.1, and 0.9.2, but due to release difficulties, we ask you not to use them.)

• Replace the built in @main method functionality with the MainArgs library

• Note that the MainArgs replacement has some backwards incompatibilities: Short flags like -i can no longer be passed via --i, the @doc("") is now @arg(doc = ""), Seq[T] parameters are now passed via repeated --foo flags rather than comma-separated.

• Add the ability to relocate/shade files in .assembly #947

• Twirl enhancements #952

• Add scalacPluginClasspath to Tests #956

• Add toMap methods to BuildInfo #958

• Bump coursier to version 2.0.0 #973

• Make BSP support a first-class citizen #969

• Omit the suffix in artifactName in cross modules #953

• Allow test classes with constructor parameters #982

• Proguard contrib module #972

• Support Scala.js useECMAScript2015 option and ModuleKind.ESModule #1004

• Support Scala.js incremental linking #1007

For details refer to milestone 0.9.3 and the list of commits.