Gradle caching mechanism

Viewed 39

It was known a while back that Gradle cached Java modules when doing incremental builds. Meaning modules A, B, & C with changes just done to A, would just require rebuilding of A alone.

However, in reading their documentation see no mention of module caching. It seems to be more general than so.

Can anyone confirm module was a thing of the past? Also if modules help reduce times with incremental builds nowadays?

1 Answers

Yes, tasks provided by Gradle itself (incl. by built-in plugins like java) generally try to be incremental, i.e., tasks with up-to-date outputs on disk won’t re-run. See also this doc section which says:

Most tasks provided by Gradle take part in incremental build because they have been defined that way.

Related