Josh Suereth d2950da9dd Fix issue where ScalaInstance broke the thread-context-classloader for all scala classes. ... 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		2014-09-09 08:56:51 -04:00
..
JUnitXmlTestsListener.scala	scalariform changes	2014-08-15 01:52:31 -04:00
TestFramework.scala	Fix issue where ScalaInstance broke the thread-context-classloader for all scala classes.	2014-09-09 08:56:51 -04:00
TestReportListener.scala	Changed to combine SuiteResult with same name, instead of replacing with latest one. This solves the test result count problem when a Suite is executed more than 1 time due to being returned as nested suites (sub-task).	2014-05-22 17:28:26 +08:00
TestStatusReporter.scala	added scalariform	2014-05-01 12:50:07 -04:00