Gradle 3.1 introduces composite builds, a feature that lets you join multiple independent Gradle builds and build them together. This solves two major pain points: the slow feedback loop when developing across multiple repositories (by replacing binary dependencies with live project dependencies via includeBuild()), and the productivity drag of large monorepos (by splitting them into independently buildable sub-projects). The feature also supports plugin development workflows and IDE integration. Planned improvements include parallel execution, continuous build integration, and richer dependency substitution APIs.
Table of contents
Table of ContentsIntroductionJoining projects #Splitting Monoliths #This is just the beginning #DiscussSort: