> > 1. I’m playing with the report configuration and I want to regenerate the > report without running the tests. >
It's a valid use case but I'm not sure if it beats the most typical use case: 'tell me the coverage'. The latter is awkwardly solved without dependsOn. Also if I want to experiment, I can always do -x test which more explicit. > 2. I’m adding a second report which aggregates several test suites > together, but I don’t want every test suite to run every time I generate > this report. > I have a feeling that this use case is unrelated: it's a custom report created by the user so he's free to lay out task relationships as he wants (be it dependsOn or mustRunAfter or nothing). So, I'm still convinced that dependsOn is better for the report task created by jacoco plugin, the one that is coupled with 'test' task. Anything else violates the principle of least surprise, will raise more questions on forums and will push the users to declare dependency explicitly in their build scripts. It's also unconventional, because 'jacocoTestReport' task (added by our plugin) clearly requires the output generated by 'test' task. For those kind of relationships, the regular the dependency is the most accurate. @Adam, in the light of my magnificent arguments, are you ok with dependsOn? :) If not, I'll respect that, close the ticket and move on to other stories. Thanks again for your input. It’s to keep from hitting the command-line limit on windows. > Ok, that's what I thought. Thanks! Cheers! -- Szczepan Faber Principal engineer@gradle; Founder@mockito
