ScalaTest seems to throw away parts of a stacked classloader about cbt HOT 2 CLOSED

Found the issue. Don't think it can be easily fixed (but I am working on a completely different approach). This issue happens when we use ScalaTest's command line runner from CBT. CBT does not have one flat classloader for everything, but builds a DAG of classloaders mirroring the dependencies. At the point we get to ScalaTest, the classloader contains only ScalaTest and it's dependencies. But ScalaTest assumes that it can find the classes to be tested on it's own classloader. ( See this https://github.com/scalatest/scalatest/blob/ed93bffc596f5e12a42396d18045bf28543bfd35/scalatest/src/main/scala/org/scalatest/tools/Runner.scala#L1524 ). In a way that does make sense for a command line runner. ScalaTest does support -R to load classes from somewhere else and they do end up in ScalaTest's classloader (see https://github.com/scalatest/scalatest/blob/ed93bffc596f5e12a42396d18045bf28543bfd35/scalatest/src/main/scala/org/scalatest/tools/Runner.scala#L1558) but none of their dependencies do, so that doesn't really help either. Closing this now, but I am currently working on ScalaTest support in a different way.

from cbt.

cc @bvenners this is what I mentioned during nescala. Found the cause now as described above.

from cbt.