On 17/05/2012, at 10:11 AM, Jeppe Nejsum Madsen wrote: > Luke Daley <[email protected]> writes: > >> Rather exciting possibility though. If I'm working in a java module >> with unit tests, I could just “liven” the test task for that module >> and achieve continuous testing (granted, you'd want to be plugged into >> a power source if you did this). I'm not aware of another tool that >> provides this feature generically, for any kind of task. > > This sounds like an awesome feature. SBT has something similar: > > https://github.com/harrah/xsbt/wiki/Triggered-Execution
Right, thanks for the pointer. The SBT implementation is slightly different to what we would likely do. In SBT it seems that you specify a bunch of files to watch for changes, and if any of them change then one or more tasks are executed. There's a nice effective simplicity to that, but it… 1. Forces you to duplicate what the inputs are to a task 2. Doesn't consider non file based changes Just adding that for completeness to this thread. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
