import org.gradle.api.internal.tasks.testing.TestResultProcessor

            plugins {
                id("gradlebuild.ci-reporting")
            }

            subprojects {
                apply(plugin = "gradlebuild.ci-reporting")
            }

            project(":failed-test-with-leftover").configureTestWithLeftover(false, true)

#### Custom Plugin and Task implementations

Build logic that is used across multiple subprojects should considered to be moved into a Gradle plugin with according Gradle task implmentation.
Elasticsearch specific build logic is located in the `build-tools-internal` subproject including integration tests.

- Gradle plugins and Tasks should be written in Java

 * called the <dfn>aggregator project</dfn> lists one or more <dfn>sub-projects</dfn>
 * which are relative pointers on the file system to other projects. This is done using
 * the {@code /project/subprojects/subproject} elements of the POM in the aggregator project.
 * Note that the aggregator project is required to have a {@code pom} packaging.</p>
 *

  ':x-pack:qa:runtime-fields:core-with-search',
  ':x-pack:qa:runtime-fields:with-security',
  ':x-pack:qa:security-example-spi-extension',
  ':x-pack:test:idp-fixture',
  ':x-pack:test:smb-fixture'
]

subprojects {
  plugins.withType(ElasticsearchJavaPlugin).whenPluginAdded {
    if (projectPathsToExclude.contains(project.path) == false) {
      project.apply plugin: "com.diffplug.spotless"


      spotless {

                    plugins {
                        base
                        kotlin("jvm") version "$embeddedKotlinVersion" apply false
                    }
                    subprojects {
                        apply(plugin = "gradlebuild.module-identity")
                        apply(plugin = "kotlin")
                        the<GradleModuleExtension>().identity.baseName.set("api-module")

        artifact-cache-metrics => artifact-cache-metrics
        artifact-cache-report => artifact-cache-report
        build/reports/configuration-cache/**/configuration-cache-report.html
        subprojects/internal-build-reports/build/reports/incubation/all-incubating.html => incubation-reports
        testing/architecture-test/build/reports/binary-compatibility/report.html => binary-compatibility-reports

    fun asConfigurationId(
        model: CIBuildModel,
        subProject: String = "",
    ): String {
        val prefix = "${testCoveragePrefix}_"
        val shortenedSubprojectName = shortenSubprojectName(model.projectId, prefix + subProject)
        return model.projectId + "_" + if (subProject.isNotEmpty()) shortenedSubprojectName else "${prefix}0"
    }

    private fun shortenSubprojectName(

          </annotations>
        </field>
        <field xdoc.separator="blank">
          <name>subprojects</name>
          <version>4.1.0+</version>
          <description>The subprojects (formerly called modules) to build as a part of this
            project. Each subproject listed is a relative path to the directory containing the subproject.
            To be consistent with the way default URLs are calculated from parent, it is recommended

### Testing changes

After making changes, you can test your code in 2 ways:

#### Run tests

- Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed. 
- For example: `./gradlew :launcher:quickTest`.

#### Install Gradle locally

and try out a change in behavior manually. 

           should manually right click on a project and
           **Gradle > Refresh Gradle Project** if the configuration is out of
           date.

As we add more subprojects you might have to re-import the gradle project (the
first step) again. There is no need to blow away the existing projects before
doing that.

### REST Endpoint Conventions