Skip to content

Commit a3e8d90

Browse files
committed
chore: minor update to gradle best practices
1 parent 11349df commit a3e8d90

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/topics/gradle/gradle-best-practices.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,8 @@ Learn more in Gradle's documentation about their [Build cache](https://docs.grad
7373
{style="note"}
7474

7575
Use the configuration cache to significantly improve build performance by caching the result of the configuration phase
76-
and reuse it for subsequent builds. If nothing changes in a build file (or its dependencies) the build file isn't
77-
recompiled.
76+
and reusing it for subsequent builds. If Gradle detects no changes in the build configuration or related
77+
dependencies, it skips the configuration phase.
7878

7979
Learn more in Gradle's documentation about their [Configuration cache](https://docs.gradle.org/current/userguide/configuration_cache.html).
8080

@@ -93,6 +93,8 @@ If you're using a library that relies on the [kapt](kapt.md) compiler plugin, ch
9393
instead. The KSP API improves build performance by reducing annotation processing time. KSP is faster and more efficient
9494
than kapt, as it processes source code directly without generating intermediary Java stubs.
9595

96+
For guidance on the migration steps, see Google's [migration guide](https://developer.android.com/build/migrate-to-ksp).
97+
9698
To learn more about how KSP compares to kapt, check out [why KSP](ksp-why-ksp.md).
9799

98100
### Use modularization
@@ -133,7 +135,7 @@ Explore Gradle's community cookbook on [Using Gradle with Continuous Integration
133135
<primary-label ref="advanced"/>
134136

135137
Like the [local build cache](#use-local-build-cache), the remote build cache helps you save time by reusing outputs
136-
from other builds. It can retrieve task outputs from any earlier build you've already run, not just the last one.
138+
from other builds. It can retrieve task outputs from any earlier build that anyone has already run, not just the last one.
137139

138140
The remote build cache uses a cache server to share task outputs across builds. For example, in a development environment
139141
with a CI/CD server, all builds on the server populate the remote cache. When you check out the main branch to

0 commit comments

Comments
 (0)