Ethan Atkins a368bf7026 Use last modified instead of hash ... I noticed that for a simple spark project that evaluating the test task was faster than running run when both tasks evaluated the same code block. I tracked this down to the BackgroundJobService.copyClasspath method. This method was hashing the jar contents of all of the files in the build. On my computer, this took 600ms (for context, the total run time of the `run` task was around 1.2 seconds, which included about 150ms of scala compiling and 350ms of time in the main method). If instead we use the last modified time it drops down to 5-10ms. As predicted, the total runtime of `run` in this project dropped down to 600ms which was on par with `test`. I am not sure why a hash was used rather than last modified in the first place, so I reworked things in such a way that, by default, sbt will use a hash but if turbo mode is on, it will use the last modified instead. We can revisit the default later.		2019-07-08 17:15:24 -07:00
..
src	Use last modified instead of hash	2019-07-08 17:15:24 -07:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00