scala – SBT：覆盖多构建dependsOn / aggregate项目中的设置

?/项目/后端/ build.sbt

name := "backend"

// old version of scala
scalaVersion := "2.9.1"

?/ mycode的/ docker_builder / build.sbt

lazy val backend = RootProject(file("~/projects/backend"))

lazy val root = (project in file(".")).
settings(
  // Doesn't work because sub-project already defines name
  name in backend := "sub-overriden",// Doesn't override {backend/}backend/*:scalaVersion since backend already defines scalaVersion in Global config
  scalaVersion in backend := "2.10.1",// Does define new setting in sub-project: {backend/}backend/test:scalaVersion (because backend did not define scalaVersion in test config)
  scalaVersion in (backend,Test) := "2.10.2"
).
aggregate(sub1)
// dependsOn(sub1)

在上面的示例中,我试图覆盖name和scalaVersion,但正如注释中所述,根项目无法覆盖后端项目中显式明确定义的任何设置/任务.现在我假设这是预期的行为,因为RootProject和它的父ProjectReference指向完全不同的SBT构建,但如果是这种情况,为什么我们允许在构建中引入新设置,例如：scalaVersion in(backend,测试)？

任何变通办法或其他解决方案？

上面的示例后端项目是一个粗略的过度简化 – 我们团队中的实际后端项目基于多项目格式,包含大约十二个子项目和sbt-plugins – 但幸运的是,我能够重现上面列出的问题.

有关：
How to define build-scoped settings in multi-project .sbt builds?
Setting javac options for SBT dependencies
Use common settings in SBT `RootProject`