On May 25, 2009, at 10:37 AM, Eske Sort wrote:
I noticed that in a project with no test-cases, the test-related
tasks are all run even though there are no tests present.
Specifically Gradle will try to execute the test-cases even though
there were no test-cases to compile (this is Gradle 0.6 - not
checked against earlier version of Gradle).
I'm not sure if skipping the execution in this case would have any
real benefit beyond the percieved (not running something that is not
needed). In any case, it seems this is something that could be
optimised slightly.
One focus of 0.7 will be to make Gradle smarter in regard to change
detection and skipping unnecessary actions. The work on that has
already started. Another improvement we want to provide for 0.7 is
smart skipping. That is to skip any task that has only the skipped
task as a dependee.
Thanks for the feedback
- Hans
Regards,
Eske
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
