Steve Appling wrote:
Tom Eyckmans wrote:
2009/5/6 Adam Murdoch <[email protected]
<mailto:[email protected]>>
<clip>
I'm curious, how we will make this available to tasks?
You'd implement a ChangeProcessor that gets notified of what has
changed, depending how the task works you can just keep a list of the
files / directories that have changed and execute the function of the
task on the list or execute the function of the task in the
ChangeProcessor methods.
Currently the change detection always scans for all files /
directories that have changed, this is not always needed so I'll add
mulitple old / new state comparison strategies. So you can have only
one event if the directory has changed in some way or for every file
/ directory that has changed.
When I was experimenting with Tom's change detection, I added a
dependsOnDir method to Task that used his ChangeProcessor. If nothing
in the dir changed, it would throw a StopExecutionException. This
seemed to work well for customizing some simple user defined tasks.
This is a good idea - it's simple, but is probably sufficient for 90% of
custom tasks.
I'm not sure about the method name - do we want to reuse 'dependsOn' or
use a different term?
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
