org.gradle.configuration-cache=true
org.gradle.configuration-cache.problems=fail
org.gradle.configuration-cache.parallel=true

# Only configure projects reachable from the requested tasks, skipping unrelated subprojects
org.gradle.isolated-projects=true

android.useAndroidX=true
kotlin.mpp.applyDefaultHierarchyTemplate=false

androidBuild=false
graalBuild=false
loomBuild=false
containerTests=false
okhttpModuleTests=false
okhttpDokka=false

**Internal properties** are not part of the Public API.
Internal properties are **unstable properties**: they CAN be renamed or removed without notice.
They are not intended for general use.
While they can be helpful in isolated cases of troubleshooting, they are intended mostly for testing or other activities within Gradle development.
The behavior behind the internal property can change at any time and without notice.

**Note**: this is a very technical detail that you probably can **just skip**.

---

The `APIRouter`s are not "mounted", they are not isolated from the rest of the application.

This is because we want to include their *path operations* in the OpenAPI schema and the user interfaces.

As we cannot just isolate them and "mount" them independently of the rest, the *path operations* are "cloned" (re-created), not included directly.

///

        }
      },
      {
        "subprojects": [
          "base-ide-plugins",
          "build-process-services",
          "docs-asciidoctor-extensions-base",
          "gradle-cli",
          "isolated-action-services",
          "logging-api",
          "plugin-use",
          "serialization",
          "time",
          "toolchains-jvm-shared",
          "versioned-cache"
        ],

testing/performance/                            @gradle/bt-developer-productivity
testing/smoke-test/                             @gradle/bt-product-operations
testing/smoke-test/src/**/*IsolatedProjects*    @gradle/bt-product-operations @gradle/bt-isolated-projects-project
testing/soak/                                   @gradle/bt-developer-productivity
testing/distributions-integ-tests               @gradle/bt-developer-productivity

  {
    "name": "io",
    "path": "platforms/core-runtime/io",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "isolated-action-services",
    "path": "platforms/core-configuration/isolated-action-services",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "ivy",
    "path": "platforms/software/ivy",

</details>

## What is a Container { #what-is-a-container }

Containers (mainly Linux containers) are a very **lightweight** way to package applications including all their dependencies and necessary files while keeping them isolated from other containers (other applications or components) in the same system.

            <option value="$PROJECT_DIR$/platforms/core-configuration/input-tracking" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/isolated-action-services" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/java-api-extractor" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl" />

    ImmutableGraph.Builder<N> transitiveClosure =
        GraphBuilder.from(graph).allowsSelfLoops(true).<N>immutable();

    for (N node : graph.nodes()) {
      // add each node explicitly to include isolated nodes
      transitiveClosure.addNode(node);
      for (N reachableNode : getReachableNodes(graph, node, strategy)) {
        transitiveClosure.putEdge(node, reachableNode);
      }
    }

# Virtual Environments { #virtual-environments }

When you work in Python projects you probably should use a **virtual environment** (or a similar mechanism) to isolate the packages you install for each project.

/// info

If you already know about virtual environments, how to create them and use them, you might want to skip this section. 🤓

///

/// tip

A **virtual environment** is different than an **environment variable**.