On 21 Nov 2013, at 2:26 am, Szczepan Faber <szczepan.fa...@gradleware.com> wrote:
> Thanks Andrew, this helps a lot. > > Jacoco report task that is introduced by our plugin is coupled with a > particular test task. There's no use case I can think of running the jacoco > report without running this test task before. Effectively, the user needs to > always include this particular test task explicitly at the command line, > which is kind of awkward (and surprising for new users). I'd like to change > this sometime this week and replace mustRunAfter with dependsOn. I'll do it > unless someone replies with a good story that supports mustRunAfter ;) There are a couple of use cases I can think of: 1. I’m playing with the report configuration and I want to regenerate the report without running the tests. 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. The pattern should be that report tasks simply report on what is already there and do no further work. Instead, it’s some lifecycle task’s business to wire the two together. In the case of reporting on the test results, we should use a finaliser to run the report task whenever the reports run. Please don’t change this to dependsOn, because the report task does not depend on the test suites that it reports on. > > @Rene, can you comment on the use of relative paths? E.g. what's the > intention? It’s to keep from hitting the command-line limit on windows. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
