This message was deleted.

I think that this configuration is broken anyway. Imagine you only run `jacocoReport`: then the task to be configured would be

jacocoReport

, which has no dependency, so the

dependsOn

wouldn't be executed. I think the reason it kind of works is because you use

map

, which will trigger eager configuration of the test tasks.

I agree! That's why I am looking for some nicer way to do this (if there is any). I don't want the dependsOn at all.

What is wrong with

jacocoReport.executionData(project.tasks.withType(Test::class.java)

?

I wasn't aware (or forgot) that this is sufficient in case of JaCoCo:

jacocoReport.executionData(project.tasks.withType(Test::class.java))

Thanks!

Not for having the task dependency, is it?

It's nicer (although you still need dependsOn)

is it sufficient? how does the report knows that it's the execution data output of the test task that it needs?

I think that's implemented it he JacocoReport task

🤔

Magic from the old Gradle days...

public void executionData(TaskCollection tasks) {
        tasks.all((Action<Task>) this::executionData);
    }

and

public void executionData(Task... tasks) {
        for (Task task : tasks) {
            final JacocoTaskExtension extension = task.getExtensions().findByType(JacocoTaskExtension.class);
            if (extension != null) {
                executionData(new Callable<File>() {
                    @Override
                    public File call() {
                        return extension.getDestinationFile();
                    }
                });
                mustRunAfter(task);
            }
        }
    }

but

all

will eagerly configure 😞

Yes. It doesn't work! Good old:

DefaultTaskCollection#all(Action) on task set cannot be executed in the current context.

This is pretty broken in the JacocoReportTask impl 😕

Oh. 😞