gradle-composite-builds

You can automate Gradle composite builds by applying includeBuild wiring and dependency substitution across multiple repositories. This skill uses settingsEvaluated and reflection to discover included projects and route artifacts to local outputs.

Dependency substitution in a Gradle composite build routes external artifacts to local project outputs. This enables rapid cross-repo iteration by automatically swapping published dependencies for local included builds.

You wire includeBuild in Gradle by applying automated repository discovery and optional substitution maps to local projects. The skill activates lifecycle-aware wiring during settingsEvaluated and rootProject phases.

If a repository clone is missing, the composite build configuration skips it automatically. The skill guards against missing clones and double-apply scenarios to maintain stable builds.

Yes, Gradle composite build wiring requires unique sanitized build names. The skill validates and enforces unique names during project discovery to prevent naming conflicts.

You need Gradle composite builds when coordinating multiple independent Gradle repositories into a coherent workspace. This approach enables cross-repo development with local project substitution without merging repositories.