Ethan Atkins 3de3cc15cf Don't use global execution context ... Because we are sharing the scala library classloader with test and run, it is possible that sbt will be competing with for resources with the test and run tasks when trying to get threads from the global execution context. Also, by using our own execution context, we can shut it down when sbt exits. The motivation for this change is that I was looking at the active jvm threads of an idle sbt process and noticed a bunch of global execution context threads.		2019-05-30 14:30:31 -07:00
..
src	Don't use global execution context	2019-05-30 14:30:31 -07:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00