Fix to issue #510 Watch doesn't detect cascading changes when nospawn is true

[bchabrier]

This fixes issue #510, by keeping the watchers when the task is running (i.e. when nospawn is used). In spawn mode, the watchers are closed and recreated as before.

I have added a test suite in nospawn_test.js, which uses grunt-contrib-copy. The test creates a source.js file, which is copied into destination.js. Without the fix, the creation of source.js is correctly detected by watch, not the creation of destination.js.

The full test suite passes on travis, but erratically fails on windows (interrupt).

Hope that helps!

[judowalker]

Is anybody going to merge this?

[ArmorDarks]

Hello?

[xgiovio]

Why is this still open?