mirror of https://github.com/sbt/sbt.git
e46843bfd9
Add a `allowUnsafeScalaLibUpgrade` setting (default is `false`) to demote the SIP-51 build failure to a warning. If the scalaVersion is 2.13.12 but some dependency pulls in scala-library 2.13.13, the compiler will stay at 2.13.12, but the dependency classpath will contain scala-library 2.13.13. This usually works, the compiler can run fine with a newer scala-library on its dependency classpath. Macro expansion may fail, if the macro uses some library class / method that doesn't exist in the old version. The macro itself is loaded from the dependency classpath into the class loader running the compiler, where the older Scala library is on the runtime classpath. Using the Scala REPL in sbt may also fail in a similar fashion. |
||
|---|---|---|
| .. | ||
| main | ||
| repo-override-test | ||
| sbt-test | ||
| test/scala/sbt | ||