Seven modules, seven copies of the same Gradle block
Copy-pasted build config drifts silently per module. A convention plugin makes the shared part shared.
gradle
15 posts
A dependency that resolves in commonMain and only exists on Android
Gradle metadata decides which variant each target gets. A library with no native artifact fails at link, not at resolution.
A version catalog is a contract, and a transitive bump breaks it quietly
Declared versions are requests, not guarantees. Resolution picks the highest.
A klib is not a jar, and that changes how dependencies resolve
Metadata, klibs and platform artifacts resolve through different Gradle variants.
The module boundary that only the build file enforced
A layering rule nobody can violate is a dependency declaration, not a document.
Why the build cache helps the JVM target and almost never the native ones
Cache keys for native compilation include the toolchain, so they rarely hit.
Gradle's configuration cache, and the one task that kept invalidating it
A task capturing Project at execution time disables it for the whole build.
Source sets are a graph, and iosMain is not where you think it is
The default hierarchy creates intermediate source sets you never declared.
appleMain exists only if your targets justify it
The hierarchy template inserts nodes based on declared targets. A directory for a node that does not exist compiles nowhere and warns about nothing.
One Gradle build, five outputs, and the cache that only helps three
Android and JVM targets cache well. Native link steps mostly do not, and that asymmetry is where your CI time goes.
A task that captures Project is a bug, not a gap
Calling it a configuration cache incompatibility frames a real defect as a missing feature. The task captures a live object where it should capture a value.
A number in CI is the only budget that holds
A budget that lives in a shared understanding has already moved. A baseline works because changing it leaves a reviewable diff with somebody's name on it.