Adam and I were talking yesterday about how to improve the skipping.
We have discussed the idea that it would be nice to skip complete
subsections of the DAG. One idea was to somehow find implicit rules on
which to decide what makes up such a subsection.
For example:
clean<-resources<-compile<-testResources<-test
install dependsOn compile, test
In such a situation we could figure out, that testResources is only
needed by the test task, and in the case the test task is skipped we
could skip testResources as well. But to just define 'install
dependsOn test', with the knowledge that compile is also executed when
test is executed, would define any subsections to skip. But in this
case I see dependsOn compile, test and dependsOn test as equivalent. I
think this should not lead to different behavior.
An alternative would be to introduce the concept of task groups. Each
task can belong to 0..n task groups and we allow to skip specific
tasks or task groups.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
