Ethan Atkins be489e05ca Clear expired loaders ... Sometimes turbo mode didn't work correctly for projects where resources were modified. This was because it was possible for the resource classloader to inadvertently evict the dependency classloader from the classloader cache because they had the same file stamps. There were two fixes: 1) remove expired entries from the cache based on the (Parent, Classpath) pair rather than just classpath 2) do not close the classloaders during cache eviction. They may still be in use when we evict them so we need to wait until they are explicitly closed elsewhere or until the go out of scope and are collected by the CleanupThread I tested this change with a spark project in which I kept modifying the resources. Prior to this change, I could get into a state where if I modified the resources, the dependency layer would get evicted every time so the benefits of turbo mode were not realized.		2019-07-29 12:30:42 -07:00
..
main	Clear expired loaders	2019-07-29 12:30:42 -07:00
test/scala/sbt	Remove matchers from MultiParserSpec	2019-06-19 16:12:45 -07:00