mirror of https://github.com/sbt/sbt.git
d2950da9dd
The issue is that when you manually set a ScalaInstance, i.e. not one from Ivy, the classpath which is returned for any given configuration ONLY uses Ivy. This means that the legitimate Scala JAR files that need to be on the classpath are missing from the list. For some reason, the way we instantiate tests uses an unfiltered classloader against the ScalaInstance, *BUT* the thread-context-classloader DOES use a filtered instance by classpath. This add the hook into the TestFramework runner creation so that the classpath accurately reflects the jars needed. cc @rkuhn |
||
|---|---|---|
| .. | ||
| appmacro/src/main/scala/sbt/appmacro | ||
| classfile | ||
| classpath | ||
| collection | ||
| complete | ||
| control | ||
| cross/src/main/input_sources | ||
| datatype | ||
| io | ||
| log | ||
| logic/src | ||
| process | ||
| relation/src | ||