diff options
author | Grzegorz Kossakowski <grzegorz.kossakowski@gmail.com> | 2015-03-09 15:11:37 -0700 |
---|---|---|
committer | Adriaan Moors <adriaan.moors@typesafe.com> | 2015-04-17 11:46:50 -0700 |
commit | ed93fac8b23b7b999ad88327beed8b2b2514d457 (patch) | |
tree | dd0e4c9f8e86578359a4b176e0f82c4569e81065 | |
parent | 6eae83a7cf62306cba1bffb0d14f2f43d377d59c (diff) | |
download | scala-ed93fac8b23b7b999ad88327beed8b2b2514d457.tar.gz scala-ed93fac8b23b7b999ad88327beed8b2b2514d457.tar.bz2 scala-ed93fac8b23b7b999ad88327beed8b2b2514d457.zip |
Avoid circular deps: override `scalaInstance`
As suggested in sbt/sbt#1872, specify ScalaInstance manually
and use sbt's launcher as a context for Ivy resolution. This way
we avoid the circular dependency problem described in the issue.
-rw-r--r-- | build.sbt | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -58,6 +58,12 @@ lazy val commonSettings = Seq[Setting[_]]( crossPaths := false, // do not add Scala library jar as a dependency automatically autoScalaLibrary := false, + // we also do not add scala instance automatically because it introduces + // a circular instance, see: https://github.com/sbt/sbt/issues/1872 + managedScalaInstance := false, + // this is a way to workaround issue described in https://github.com/sbt/sbt/issues/1872 + // check it out for more details + scalaInstance := ScalaInstance(scalaVersion.value, appConfiguration.value.provider.scalaProvider.launcher getScala scalaVersion.value), // we always assume that Java classes are standalone and do not have any dependency // on Scala classes compileOrder := CompileOrder.JavaThenScala, |