Composite build dependency resolution

I have a project that is composed of other projects using includeBuild, most of which are “simple” projects, but a few are projects that have multiple sub-projects (via include). I’m trying to find a way to enforce rules on dependencies defined in all projects, such that when I build from the top-level, the rules will be applied and prevent builds from succeeding if the rules are broken. For example, enforcing a fixed version of Guava, or excluding a particular transient dependency for every includedBuild – is this possible?


  • Matt