This message was deleted.

You would probably need a custom task and use

copy { ... }

in it's action multiple times for multiple destination. But that would not run in parallel. For parallel execution you would then additionally have to use the worker API, so that the "subtasks" can be run in parallel. Another option would be to declare multiple tasks and use configuration cache, so that the tasks can run in parallel.

Hmmm... sounds a bit complicated. Do you think it also can work if I just register a simple task, and in the

doLast

block I just code up some kotlin code that using copyToRecursively and perhaps some parallel stream to get the work done? The destination folders are completely outside of rootDir so the gradle build does not need to be aware of the side effect.

Probably

Otherwise ideally the copy task API should support this, I guess 😛

Feel free to open a feature request for it. I don't think it should, but who am I to judge. Request it and see what the Gradle folks think about it. 🙂

I see, thanks. Perhaps I should. In our use case is that the jars we produced from the java repos are part of a large application, so in local dev after we build all the jars, in order to run the app, we need to fetch lots of other resources (sync one a day perhaps) and combine the jars with those so we can run the whole app. Maybe it is not some typical case out there:)