- 2-3 Senior Java developers with SMB protocol expertise
- 1 QA engineer for test infrastructure
- 1 DevOps engineer for CI/CD setup

### Timeline
- **Total Duration**: 6-8 months for all features
- **Phases 1-2**: 2-3 months (High priority)
- **Phases 3-4**: 2 months (Medium priority)
- **Phases 5-6**: 2-3 months (Low priority)

### Infrastructure
- Windows Server test lab
- RDMA-capable test hardware

#### 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

# Using MinIO with Veeam

When using Veeam Backup and Replication, you can use S3 compatible object storage such as MinIO as a capacity tier for backups.  This disaggregates storage for the Veeam infrastructure and allows you to retain control of your data. With the ease of use of setup and administration of MinIO, it allows a Veeam backup admin to easily deploy their own object store for capacity tiering.

## Prerequisites

### 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.

## Structure

          "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"
        }

1. Generate the node's keystore:
   `keytool -genkey -alias test-node -keystore test-node.jks -keyalg RSA -keysize 2048 -validity 3654 -dname CN="Elasticsearch Build Test Infrastructure" -keypass keypass -storepass keypass -ext san=dns:localhost,dns:localhost.localdomain,dns:localhost4,dns:localhost4.localdomain4,dns:localhost6,dns:localhost6.localdomain6,ip:127.0.0.1,ip:0:0:0:0:0:0:0:1`

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.

> In a cloud-native environment, scalability is not a function of the application but the orchestration platform.

In a typical modern infrastructure deployment, application, database, key-store, etc. already live in containers and are managed by orchestration platforms. MinIO brings robust, scalable, AWS S3 compatible object storage to the lot.

## 1. Prefer team ownership over individual user ownership.
## 2. GBT-related team should be listed first.
## 3. Try to keep paths alphabetically sorted within visual groups.
## 4. List individual owners last.
##

# Build infrastructure
.teamcity/                                  @gradle/bt-developer-productivity

import org.apache.maven.api.annotations.Consumer;
import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.ThreadSafe;

/**
 * Represents the contract for Mojos to interact with the Maven infrastructure.
 * Implementations of this interface define specific build-process behaviors
 * that are triggered during a Maven build lifecycle.
 *
 * The primary entry point is the {@link #execute()} method, which encapsulates