Miscellaneous machinery around traversing & querying the build hierarchy, that should not be needed by normal users of Mill

Bind a dependency (Dep) to the actual module contetxt (e.g. the scala version and the platform suffix)

Customize the coursier file cache.

This is rarely needed to be changed, but sometimes e.g you want to load a coursier plugin. Doing so requires adding to coursier's classpath. To do this you could use the following:

override def coursierCacheCustomizer = T.task {
   Some( (fc: coursier.cache.FileCache[Task]) =>
     fc.withClassLoaders(Seq(classOf[coursier.cache.protocol.S3Handler].getClassLoader))
   )
}

Map dependencies before resolving them. Override this to customize the set of dependencies.

Customize the coursier resolution resolution process. This is rarely needed to changed, as the default try to provide a highly reproducible resolution process. But sometime, you need more control, e.g. you want to add some OS or JDK specific resolution properties which are sometimes used by Maven and therefore found in dependency artifact metadata. For example, the JavaFX artifacts are known to use OS specific properties. To fix resolution for JavaFX, you could override this task like the following:

override def resolutionCustomizer = T.task {
  Some( (r: coursier.core.Resolution) =>
    r.withOsInfo(coursier.core.Activation.Os.fromProperties(sys.props.toMap))
  )
}

Task that resolves the given dependencies using the repositories defined with repositoriesTask.