}

    def "Multi-project build can define different target bytecode level for subprojects"() {
        given:
        createDirs("subproject-a", "subproject-b", "subproject-c")
        settingsFile << """
            include 'subproject-a', 'subproject-b', 'subproject-c'
        """

        buildFile << """
            project(':subproject-a') {
                apply plugin: 'java'

<project>
    <property name="lib.dir" location="lib/test"/>

<% ['clean', 'jar', 'build'].each { target -> %>
    <target name="$target">
        <% subprojects.each { subproject -> %>
            <ant dir="$subproject" target="$target">
                <property name="lib.dir" location="\${lib.dir}"/>
            </ant>
        <%  } %>
    </target>
<% } %>

<3> Gradle wrapper scripts
<4> Gradle settings file to define a root project name and subprojects
<5> Gradle build scripts of the two subprojects - `subproject-a` and `subproject-b`
<6> Source code and/or additional files for the projects

== Invoking Gradle

=== IDE

This sample shows how to aggregate test results across multiple Java subprojects.  The link:{userManualPath}/test_report_aggregation_plugin.html[test-report-aggregation plugin] provides this ability when applied to the distribution project, such as an Android application or WAR subproject.

This sample shows how to aggregate code coverage across multiple Java subprojects using link:https://www.jacoco.org/jacoco/[JaCoCo].  The link:{userManualPath}/jacoco_report_aggregation_plugin.html[jacoco-report-aggregation plugin] provides this ability when applied to the distribution project, such as an Android application or WAR subproject.

        settingsFile << """
            rootProject.name = 'root'
            include '1', '2'
        """
        buildFile << """
            subprojects {
                task otherBuild(type:GradleBuild) {
                    dir = "\${rootProject.file('subprojects')}"
                    tasks = ['log']
                    buildName = project.name + "nested"
                    def startEvent = project.name + "-started"

    def "will substitute and run build dependencies for closed projects on startup"() {
        setup:
        multiProjectBuildInRootFolder("parent", ["child1", "child2"]) {
            buildFile << """
            subprojects {
                apply plugin: 'java-library'
            }
            project(":child1") {
                configurations {
                    testArtifacts
                }

plugins {
    id("gradlebuild.collect-failed-tasks")
    id("gradlebuild.cache-miss-monitor")
}

description = "Provides plugins that are used by Gradle subprojects"

tasks.register("check") {
    dependsOn(subprojects.map { "${it.name}:check" })
}

val clean by tasks.registering {
    val buildLogicPropertiesFile = layout.projectDirectory.file("gradle.properties")
    val rootPropertiesFile = layout.projectDirectory.file("../gradle.properties")

plugins {
  id("com.vanniktech.maven.publish.base")
  id("java-platform")
}

dependencies {
  constraints {
    project.rootProject.subprojects.forEach { subproject ->
      if (subproject.name != "okhttp-bom") {
        api(subproject)
      }
    }
  }
}

publishing {
  publications.create<MavenPublication>("maven") {
    from(project.components["javaPlatform"])
  }

    @ToBeFixedForIsolatedProjects(because = "subprojects")
    def "build is not exponentially slower when many tasks are requested"() {
        createDirs((1..30).collect({ "sub" + it }) as String[])
        settingsFile << """
            rootProject.name = "test"
            (1..30).each {
                include "sub" + it
            }
        """
        buildFile << """
            subprojects {
                apply plugin: 'java'