Closed nicolasstucki closed 6 years ago
This should be reproducible on https://github.com/nicolasstucki/dotty-project/tree/scalacheck using sbt test
.
slowActualVersion
is only called if fastActualVersion
fails, this should not happen because the dotty jar should contain a compiler.properties
file with the correct content ever since fc3221836bd28c98dbef64e564d6f4e8b6ae90db. Maybe when running the test the dotty jar is not present on the classpath?
Closing because this doesn't seem to be happening anymore.
I found this while executing tests using sbt-dotty.
The issue is that sbt tries to fetch the version from scala.tools.nsc.Properties throug reflection.
Code in
sbt.ScalaInstance.slowActualVersion
that call it is:The stacktrace is:
One hacky work around that I found is to add the following class in dotty