<resources>
      <resource>
        <directory>res/main</directory>
        <filtering>true</filtering>
        <targetPath>main</targetPath>
        <includes>
          <include>main.included</include>
        </includes>
        <excludes>
          <exclude>main.excluded</exclude>
        </excludes>
      </resource>
    </resources>
    <testResources>
      <testResource>

    def setup() {
        createDirs("sub", "included", "included/sub")
        settingsFile << """
            rootProject.name = 'root'
            include('sub')
            includeBuild('included')
        """
        file('included/settings.gradle') << """
            include('sub')
        """
        buildFile << """
            def test = tasks.register('test') {

== Using separate composite build

It is also possible to create a separate composite build that includes both the `my-app` and `my-utils` builds.

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

After doing so, you can reference any tasks in the included builds directly on the command line in order to execute.

```
gradle :my-app:app:run
```

     * <pre class='autoTestedSettings'>
     *   // include two projects, 'foo' and 'foo:bar'
     *   // directories are inferred by replacing ':' with '/'
     *   include 'foo:bar'
     *
     *   // include one project whose project dir does not match the logical project path
     *   include 'baz'
     *   project(':baz').projectDir = file('foo/baz')
     *

    /**
     * Returns the included builds that were referenced by this build. This is the set of builds that were directly included by this build via its {@link org.gradle.api.initialization.Settings} instance.
     *
     * <p>Note that this set does not include builds that are added in other ways, such as a `buildSrc` build.

In this example, the root settings file will look as follows:

.settings.gradle.kts
[source,kotlin]
----
include("mobile-app", "web-app", "api", "lib", "documentation")
----

NOTE: The order in which the subprojects (modules) are included does not matter.

The `buildSrc` directory is automatically recognized by Gradle.

The build is configured as follows:
====
include::sample[dir="kotlin",files="settings.gradle.kts[]"]
include::sample[dir="groovy",files="settings.gradle[]"]
====

The shared _convention plugin_ `myproject.java-conventions` is implemented in an _included build_ called `build-conventions`.
The build is then included in the root project's _settings_ file as seen in the above snippet.

    def "recompiles source file when transitively included header file is changed"() {
        given:
        def transitiveHeaderFile = file("src/main/headers/transitive.h") << """
           // Dummy header file
"""
        otherHeaderFile << """
            #include "${transitiveHeaderFile.name}"
"""
        sourceFile << """
            #include "${otherHeaderFile.name}"
"""

        and:

John Howard <******@****.***> 1565919828 -0700

John Howard <******@****.***> 1565919828 -0700