From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

If after tasks is good too, yes. For before I think no

problem I need to copy files before another task is running

```target.gradle.taskGraph.beforeTask { task -&gt;
    if (task.name == "some name") {
        // add files to build/some-dir
    }
}```

Sounds like you definitely should not do that anyway

But other than that, you could just register a `doFirst` action with the task in question

This should be the same then?

```val task =
    target.tasks.named("some name").apply {
        configure {
            it.doFirst {
                // add files to build/some-dir
            }
        }
    }```


```DefaultTaskContainer#NamedDomainObjectProvider.configure(Action) on task set cannot be executed in the current context.```

So, you can configure another task, but you can't do it, for example, from another task

Yeah, the problem this was a mess, I am refactoring instead of trying to get it working because it is awful to maintain at this moment

&gt; So, you can configure another task, but you can't do it, for example, from another task
Of course you can, as long as you don't need configuration cache compatibility.
But most often there are better ways.