mill.scalalib

Shared logic between the different kinds of cross-scala-version modules: CrossSbtModule, CrossScalaModule

A CrossScalaModule with the SbtModule source file layout: src/main/java, src/test/resources, etc.

A ScalaModule which is suited to be used with mill.api.Cross. It supports additional source directories with the scala version pattern as suffix (src-{scalaversionprefix}), e.g.

• src
• src-2.11
• src-2.12.3

Adds version range specific sources when mixed-in to a cross module like CrossScalaModule or CrossSbtModule. It is useful when a Scala version specific breaking change requires two implementations of the same code for the cross versions before and after a specific version. For example, migrating to Scala 2.13 it is usually needed to define some version specific code for Scala 2.12- (all the versions less or equal 2.12) and for Scala 2.13+ (all the versions greater or equal to 2.13). Mixing CrossScalaVersionRanges into a CrossScalaModule will automatically add the src-2.13+ and src-2.12-, based on the crossScalaVersion.

A ScalaModule intended for defining .jvm/.js/.native submodules It supports additional source directories per platform, e.g. src-jvm/ or src-js/ and can be used inside a CrossScalaModule.Base, to get one source folder per platform per version e.g. src-2.12-jvm/.

Adjusts the moduleDir and artifactNameParts to ignore the last path segment, which is assumed to be the name of the platform the module is built against and not something that should affect the filesystem path or artifact name

A ScalaModule with sbt compatible directory layout.

Core configuration required to compile a single Scala module

Mix this in to any ScalaModule to provide a unidocSite task that can be used to build a unified scaladoc site for this module and all of its transitive dependencies