Hey, I have a couple of questions re jacoco:
- jacoco tasks don't depend on test tasks. So running 'jacoco' has no effect (task is skipped). Is this intentional? I think jacoco report task should depend on test task that produces the input. - the agent arguments use relative paths. What is the reason of using relative paths? Is it to conserve the length of the args? If absolute paths are used, it's easier to hook up jacoco for e2e integration tests (e.g. container needs to start with agent settings) because the getAsJvmArgs() method can be used to build agent arguments. - some html reports allow to navigate to the class level and inspect the class visually, by looking at decorated source file. However some classes are not decorated - e.g. I can only see the tabular view of the coverage, but cannot drill down to the decorated source file. I haven't figured out the pattern of when it works or not. Anyone knows about this issue? - I've noticed that doFirst() is used to configure test tasks' jvmargs. Currently, the up-to-date checks don't work reliably when task inputs or outputs are changed during this task execution. Cheers! -- Szczepan Faber Principal engineer@gradle; Founder@mockito
