Ethan Atkins fd2ec7adc3 Fix '~' for dependent projects with a broken parent ... In #4446, @japgolly reported that in some projects, if a parent project was broken, then '~' would immediately exit upon startup. I tracked it down to this managed sources filter. The idea of this filter is to avoid getting stuck in a build loop if managedSources writes into an unmanaged source directory. If the (managedSources in ThisScope).value line failed, however, it would cause the watchSources, and by delegation, watchTransitiveSources task to fail. The fix is to only create this filter if the managedSources task succeeds. I'm not 100% sure if we shouldn't just get rid of this filter entirely and just document that '~' will probably loop if a build writes the result of managedSources into an unmanaged source directory.		2018-11-11 09:36:46 -08:00
..
src	Fix '~' for dependent projects with a broken parent	2018-11-11 09:36:46 -08:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00