{
        "subprojects": [
          "declarative-dsl-provider",
          "declarative-dsl-tooling-builders",
          "enterprise",
          "execution-e2e-tests",
          "file-collections",
          "ide-plugins",
          "integ-test",
          "ivy",
          "jacoco",
          "kotlin-dsl-tooling-builders",
          "language-groovy",
          "maven",
          "platform-native",

            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-builders" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-model-impls" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-models" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/model-core" />

  {
    "name": "tooling-api-provider",
    "path": "platforms/core-runtime/tooling-api-provider",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "tooling-native",
    "path": "platforms/native/tooling-native",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": true
  },
  {
    "name": "tooling-native-model-impls",

  stars: 3501
  owner_login: IBM
  owner_html_url: https://github.com/IBM
- name: opyrator
  html_url: https://github.com/ml-tooling/opyrator
  stars: 3137
  owner_login: ml-tooling
  owner_html_url: https://github.com/ml-tooling
- name: docarray
  html_url: https://github.com/docarray/docarray
  stars: 3120
  owner_login: docarray
  owner_html_url: https://github.com/docarray

platforms/core-configuration/kotlin-dsl-plugins/            @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-provider-plugins/   @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-tooling-builders/   @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-tooling-models/     @gradle/bt-tide

# Core automation platform (Declarative DSL)
platforms/core-configuration/declarative-dsl-api/                   @gradle/bt-declarative-gradle-project

        )

        // TODO: Gradle profiler should use the bundled tooling API.
        //   This should actually be handled by conflict resolution, though it doesn't seem to work.
        //   See https://github.com/gradle/gradle/issues/12002.
        applyRule<DependencyRemovalByNameRule>(
            "org.gradle.profiler:gradle-profiler",
            setOf("gradle-tooling-api")
        )
    }
}

    <!-- Protocol types may only define constants in interfaces -->
    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]tooling-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]tooling[/\\]internal[/\\]protocol.+"/>
    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]core-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]attributes[/\\]Usage.+"/>

}

interface ModuleTargetRuntimes {

    /**
     * Declare that this Gradle module runs as part of the wrapper or as part of a client process.
     * Client processes include the Tooling API client or the CLI client.
     */
    val client: Property<Boolean>

    /**
     * Declare that this Gradle module runs as part of the Gradle daemon.
     */
    val daemon: Property<Boolean>

Wie funktioniert das? Schauen wir uns das mal an. 🤓

### Typannotationen und Tooling { #type-annotations-and-tooling }

Sehen wir uns zunächst an, wie Editor, mypy und andere Tools dies sehen würden.

    }

    /**
     * Careful here: if threads are mutating the atomicLongArray while this method is executing, the
     * final long[] will be a "rolling snapshot" of the state of the bit array. This is usually good
     * enough, but should be kept in mind.
     */
    public static long[] toPlainArray(AtomicLongArray atomicLongArray) {