sbt/project
Eugene Yokota de20328029 Let ++ fall back to a bincompat Scala version
Fixes https://github.com/sbt/sbt/issues/7327

**Problem**
In builds with mixed Scala patch versions (like scalameta),
it's possible for a core subproject to be set to the lastest 2.12.x,
but the compiler plugin component is cross published to 2.12.0 etc.
`++ 2.12.0` in this case does not work since sbt 1.7.x onwards requires
the queried Scala version to be listed in `crossScalaVersions`.

**Solution**
This implements sbt 1.6.x-like fallback mechanism,
but instead of using the queried version (e.g. 2.12.0) it will set
the Scala version to one of listed versions that is binary compatible.
2023-07-09 18:31:55 -04:00
..
ContrabandConfig.scala Adjust to upstream changes 2017-07-16 00:51:49 -04:00
Dependencies.scala Zinc 1.9.2 2023-06-25 23:01:45 -04:00
Docs.scala Cleanup project/Transform.scala 2019-11-28 21:25:49 +00:00
HouseRulesPlugin.scala Update build settings for Scala 3 2021-11-16 10:19:26 +09:00
NightlyPlugin.scala Port mutable.Specification to verify.BasicTestSuite 2021-01-16 00:47:53 -05:00
PublishBinPlugin.scala Use sbt 1.5.1 2021-05-02 23:41:55 -04:00
SbtLauncherPlugin.scala Use sbt 1.5.1 2021-05-02 23:41:55 -04:00
Scripted.scala Use Array to talk to proper build 2020-03-18 16:28:51 -04:00
Transform.scala Run scalafmtSbt 2019-11-30 14:57:57 -08:00
Util.scala Use sbt 1.5.1 2021-05-02 23:41:55 -04:00
build.properties Let ++ fall back to a bincompat Scala version 2023-07-09 18:31:55 -04:00
flamegraph_svg.png document profiling tools 2018-04-04 01:29:56 -04:00
plugins.sbt remove sbt-whitesource 2022-07-03 14:45:23 +09:00