From 30e2362d0a16e3f61d010080e3b3eccdf84f7c7e Mon Sep 17 00:00:00 2001 From: Iulian Dragos Date: Thu, 6 Jul 2017 12:27:12 +0200 Subject: [PATCH] Use `scalaOrganization` when adding the compiler dependency Sbt has a setting for controlling the Scala organization, and it allows people to use the Typelevel compiler, for instance. We use the same mechanism in Hydra, and this will allow everyone to use the same benchmark code. --- build.sbt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/build.sbt b/build.sbt index 6dd12d0..1a1f48f 100644 --- a/build.sbt +++ b/build.sbt @@ -36,13 +36,13 @@ lazy val compilation = addJmh(project).settings( // We should be able to switch this project to a broad range of Scala versions for comparative // benchmarking. As such, this project should only depend on the high level `MainClass` compiler API. description := "Black box benchmark of the compiler", - libraryDependencies += "org.scala-lang" % "scala-compiler" % scalaVersion.value, + libraryDependencies += scalaOrganization.value % "scala-compiler" % scalaVersion.value, mainClass in (Jmh, run) := Some("scala.bench.ScalacBenchmarkRunner") ).settings(addJavaOptions).dependsOn(infrastructure) lazy val micro = addJmh(project).settings( description := "Finer grained benchmarks of compiler internals", - libraryDependencies += "org.scala-lang" % "scala-compiler" % scalaVersion.value + libraryDependencies += scalaOrganization.value % "scala-compiler" % scalaVersion.value ).settings(addJavaOptions).dependsOn(infrastructure) lazy val jvm = addJmh(project).settings(