You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It only has an effect if the Scala version number is exactly
2.11.0-SNAPSHOT. For 2.11.x-SNAPSHOT with x > 0, sbt already sets
the scalaBinaryVersion to 2.11.
Note that our nightly release builds don't use -SNAPSHOT for the
Scala version, but something like 2.12.0-[sha]-nightly.
// TODO add doc. not sure i really see the valid use case for this feature. yet.
8
-
// - only relevant for x.y.0-SNAPSHOT, once x.y.0 is out, the binary ver of x.y.1-SNAPSHOT is x.y (patch is dropped)
9
-
// - used when publishing using a scala snapshot. the module will not have SNAPSHOT in the scala binary version.
10
-
// allows using a snapshot of the module more easily. eg if you're using scala 2.12.0-M1, you can say "org.scala-lang.modules" %% "scala-xml" % "1.0.2-SNAPSHOT"
11
-
// - also used to resolve dependencies of modules. when building with a snapshot scala, deps will be resolved against this binver.
12
-
valsnapshotScalaBinaryVersion= settingKey[String]("The Scala binary version to use when building against Scala SNAPSHOT.")
13
7
valrepoName= settingKey[String]("The name of the repository under github.com/scala/.")
14
8
valmimaPreviousVersion= settingKey[Option[String]]("The version of this module to compare against when running MiMa.")
15
9
16
10
privatevalcanRunMima= taskKey[Boolean]("Decides if MiMa should run.")
17
11
privatevalrunMimaIfEnabled= taskKey[Unit]("Run MiMa if mimaPreviousVersion and the module can be resolved against the current scalaBinaryVersion.")
18
12
19
-
defderiveBinaryVersion(sv: String, snapshotScalaBinaryVersion: String) = sv match {
0 commit comments