[GRADLE-533] Initial Framework for Task Optimization Created: 29/Jun/09 Updated: 04/Jan/13 Resolved: 01/Jul/09
|Reporter:||Steve Appling||Assignee:||Hans Dockter|
Add the initial framework for specification of manual optimization criteria as discussed in the thread at http://www.nabble.com/Task-Optimization-to24117691.html
This patch adds:
It does not have any updates for the documentation.
I would like to try to pursue (in the next step) how to have more useful built in optimizations for Java and Groovy plugins.
|Comment by Adam Murdoch [ 01/Jul/09 ]|
I'm not sure about the new command-line option. Why do we need it?
|Comment by Steve Appling [ 02/Jul/09 ]|
The new command line option was added for the case where the onlyIf optimization is not be 100% correct. There will be items that can change that may not allow a task to run when it should. For example, you may not pick up build.gradle changes that should force the task to re-run. This allows you to force the tasks to run without having to do a clean. A clean build for a big system can be very expensive (ours is over 10 minutes).
That being said, it is really optional. You can accomplish the same thing with clean. I also do not like the large number of command line options that we currently have. I hope that some of them can be simplified (or removed) when the command line syntax is reviewed.