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

Gradle Community

I just discovered that archive `AbstractCopyTask`, disable output caching if you call some methods, `fileMatching` for example. I would think it has to do with the action serializibility.

<https://github.com/gradle/gradle/commit/510d032ec36b9302a6a026335f39042ced058c60#diff-d69c80c6a073b8312669ecf3a84ab1f92507076a683ef17e0596b74fe349cedf|github.com/gradle/gradle/commit/510d032ec36b…#…>

Maybe this can even be removed in the meantime with all those changes done for CC and so on :man-shrugging:

But no idea whether <@UA7A3BLL8> still knows the details of 10 years ago.
I don't find an issue or pr for that

I was kind surprised though about this behavior for simple lambdas. Especially since I believe the closure lamnda serialization improved a lot in 10 years

if a lambda captures unserializable types like `project` then that's a problem with CC. but some of them (`filter([map, ]class)`, `expand(map)`, `rename({string|regex}, string)`) aren't lambdas that could capture. so even more so than the other methods, I don't see why they should prevent caching

Maybe it's expected that they do unforeseeable things :man-shrugging:

Also there's <https://docs.gradle.org/current/userguide/build_cache.html#:~:text=Some%20tasks%2C%20like%20Copy%20or%20Jar%2C%20usually%20do%20not%20make%20sense%20to%20make%20cacheable%20because%20Gradle%20is%20only%20copying%20files%20from%20one%20location%20to%20another.%20It%20also%20doesn%E2%80%99t%20make%20sense%20to%20make%20tasks%20cacheable%20that%20do%20not%20produce%20outputs%20or%20have%20no%20task%20actions.|that>, so maybe things won't change as much.

For the built-in tasks, yes, nothing should change