(Option?) to stop application on compile errors

[axos88]

Hello,

I would like to be able to configure revolver in a way that it would stop the application on compile errors.

Eg:

sbt ~re-start
// application runs, start implementing new feature
// make changes to the code, but accidentally break compilation
// recompilation triggered, and it fails

At this point I would expect the application running in the background to stop running. I am developing a webapp, so I expect navigating to the correct address to give an unable to connect error.

What happens is that the former version keeps on running, and unless I take a good look at the compilation output, I am interacting with the old version, and wondering why my changes are not taking any effect

[axos88]

@jrudolph

[jrudolph]

I agree that this would be nice to have.

[matanox]

Just looking around, I think this should only be optional or at least governed by a flag. In my flows, restarting the server when code is broken can be misleading and (very) unproductive. I don't think we should have a single semantics fits all philosophy here.

[axos88]

Just searched for this again, and stumbled upon my own issue report here :(