include::sample[dir="groovy",files="settings.gradle[]"]
====

.Producer's build
====
include::sample[dir="kotlin",files="producer/build.gradle.kts[]"]
include::sample[dir="groovy",files="producer/build.gradle[]"]
====

.Consumer's build
====
include::sample[dir="kotlin",files="consumer/build.gradle.kts[]"]
include::sample[dir="groovy",files="consumer/build.gradle[]"]
====

See also:

== Step 7. Understanding the Build script
Each subproject contains its own `build.gradle(.kts)` file.

The `build.gradle(.kts)` file is the core component of the build process and defines the tasks necessary to build the project.

The `build.gradle(.kts)` file is read and executed by Gradle.

Take a closer look at the build file in your `app` subproject (under the `app` directory):

    }


    def "emits test operations as expected for two builds in a row"() {
        given:
        executer.withRepositoryMirrors()
        resources.maybeCopy('TestExecutionBuildOperationsIntegrationTest/emitsBuildOperationsForJUnitTests')

        when:
        run "test"

        then: "test build operations are emitted in expected hierarchy"

 * Build root directories are always watchable hierarchies.
 * Watching the build root directories is better since they are less likely to be deleted and
 * nearly no changes to the watched directories are necessary when running builds on the same project.
 *
 * To allow deleting the build root directories, we need to stop watching a build root directory if there are no more snapshots in the VFS inside,

        val builds = mutableMapOf<BuildState, BuildToStore>()
        host.visitBuilds { build ->
            val state = build.state
            builds[state] = BuildToStore(build, build.hasScheduledWork, build.isRootBuild)
            if (build.hasScheduledWork && state is StandAloneNestedBuild) {
                // Also require the owner of a buildSrc build

3. You learned about dependency management in <<part3_gradle_dep_man#part3_begin,part 3>>.
4. You applied a plugin to your app in <<part4_gradle_plugins#part4_begin,part 4>>.
5. You learned about incremental builds in <<part5_gradle_inc_builds#part5_begin,part 5>>.
6. You turned on the local cache in <<part6_gradle_caching#part6_begin,part 6>>.

== Step 1. Gradle References
To work with Gradle, the following references are useful:

@TargetGradleVersion('>=3.3')
class DisabledTaskExecutionOnIncludedBuildsCrossVersionSpec extends ToolingApiSpecification {

    @TargetGradleVersion('>=3.3 <6.8')
    def "Can't launch tasks from included builds via launchables obtained from GradleProject model"() {
        setup:
        singleProjectBuildInRootFolder("root") {
            settingsFile << """
                includeBuild 'includedBuild'
            """
        }

    /**
     * Includes a plugin build at the specified path to the composite build.
     * Included plugin builds can contribute settings and project plugins.
     * @param rootProject The path to the root project directory for the build.
     *
     * @since 7.0
     */
    @Adding
    void includeBuild(String rootProject);

    /**

					"jacoco",
					"launcher",
					"plugins-java",
					"antlr",
					"base-services",
					"build-cache",
					"build-cache-http",
					"build-cache-local",
					"build-cache-spi",
					"build-configuration",
					"build-events",
					"build-init",
					"build-profile",
					"composite-builds",
					"configuration-cache",
					"core",
					"core-api",
					"declarative-dsl-core",

Paths
     :api:libs
     :webapp:libs

Type
     Task (org.gradle.api.Task)

Options
     --rerun     Causes the task to be re-run even if up-to-date.

Description
     Builds the JAR

Group