#### IDE integration

Provides cross-cutting integration with IDEs and other tooling.

#### Build infrastructure

Provides build logic, libraries, test suites and infrastructure to support developing and releasing Gradle.

#### Documentation

Provides cross-cutting Gradle documentation and samples, along with the infrastructure to write, test, publish and host the documentation.

## Consequences

          "stdlib-java-extensions",
          "stdlib-kotlin-extensions",
          "test-kit",
          "test-suites-base",
          "testing-base",
          "testing-base-infrastructure",
          "testing-jvm-infrastructure",
          "testing-native",
          "time",
          "toolchains-jvm"
        ],
        "parallelizationMethod": {
          "name": "TestDistributionAlpine"
        }

When sharing data with external tools, we use JSON.

## Consequences

* The configuration cache serialization infrastructure should be used for all serialization.
* Existing usages of Serializer outside of this infrastructure should be migrated to use it.
* Existing usages of Java serialization should be migrated to use it.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.

The UI architecture module uses the core runtime architecture module. It provides APIs that are used by the other modules and platforms. 

    }

    @Test
    public void test_nullSafeLogout() {
        SpnegoAuthenticator authenticator = new SpnegoAuthenticator();

        // SPNEGO logout should return null (relies on Kerberos infrastructure)
        String logoutUrl = authenticator.logout(null);
        assertNull(logoutUrl);
    }

    @Test
    public void test_nullSafeGetResponse() {

    "path": "platforms/software/testing-base",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-base-infrastructure",
    "path": "platforms/software/testing-base-infrastructure",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-jvm",
    "path": "platforms/jvm/testing-jvm",

│   ├── service/               # Business logic services
│   ├── pager/                 # Pagination handlers
│   └── job/                   # Background jobs
├── api/                       # REST API infrastructure
├── opensearch/                # DBFlute integration for OpenSearch
│   ├── config/                # Config index (crawl configs, schedules)
│   ├── log/                   # Log index (search logs, click logs)

            <option value="$PROJECT_DIR$/platforms/jvm/scaladoc-worker" />
            <option value="$PROJECT_DIR$/platforms/jvm/testing-jvm" />
            <option value="$PROJECT_DIR$/platforms/jvm/testing-jvm-infrastructure" />
            <option value="$PROJECT_DIR$/platforms/jvm/toolchains-jvm" />
            <option value="$PROJECT_DIR$/platforms/jvm/toolchains-jvm-shared" />
            <option value="$PROJECT_DIR$/platforms/jvm/war" />

    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]software[/\\]testing-base-infrastructure[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]tasks[/\\]testing[/\\][^/\\]+"/>

    <!-- These packages are duplicated in workers and daemon-server-worker, don't require a package-info.java in each place -->

## Install using Helm Charts

There are two paths for installing MinIO onto Kubernetes infrastructure:

- Use the [MinIO Operator](https://github.com/minio/operator)
- Use the community-maintained [Helm charts](https://github.com/minio/minio/tree/master/helm/minio)