/libraries/maven-settings.xml "Kotlin Build Infrastructure"
/libraries/pom.xml "Kotlin Build Infrastructure"
/libraries/mvnw "Kotlin Build Infrastructure"
/libraries/mvnw.cmd "Kotlin Build Infrastructure"
/libraries/.mvn/wrapper/maven-wrapper.properties "Kotlin Build Infrastructure"
/libraries/ReadMe.md A.Qurbonzoda Vsevolod.Tolstopyato Ilya.Gorbunov Filipp.Zhinkin

/license/ "Kotlin Build Infrastructure"

/native/ "Kotlin Native"

# Keys like `- build_infrastructure:` do not mean anything, they just need to be unique
# The `name:` field specifies the platform label, e.g. `name: build_infrastructure` => `platform:build_infrastructure` label
platforms:
  - build_infrastructure:
    name: 'build_infrastructure'
  - core_configuration:
    name: 'core_configuration'
  - core_execution:

native --> core
native --> software

enterprise["enterprise module"]
style enterprise stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px;

build_infrastructure["build-infrastructure module"]
style build_infrastructure stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px;

    testImplementation(projectTests(":compiler:tests-common"))
    testApi(projectTests(":compiler:test-infrastructure-utils"))
    testApi(projectTests(":compiler:test-infrastructure"))
    testImplementation(projectTests(":compiler:tests-common-new"))
    testImplementation(projectTests(":analysis:analysis-api-impl-barebone"))

- [ ] Ambient
- [ ] Configuration Infrastructure
- [ ] Docs
- [ ] Dual Stack
- [ ] Installation
- [ ] Networking
- [ ] Performance and Scalability
- [ ] Policies and Telemetry
- [ ] Security
- [ ] Test and Release
- [ ] User Experience
- [ ] Developer Infrastructure

**Please check any characteristics that apply to this pull request.**

# Keys like `- build_infrastructure:` do not mean anything, they just need to be unique
# The `name:` field specifies the platform label, e.g. `name: build_infrastructure` => `platform:build_infrastructure` label
platforms:
  - bt_ge_build_cache:
    name: 'bt_ge_build_cache'
    subprojects:

    native --> core
    native --> software

    enterprise["enterprise module"]
    style enterprise stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px,color:#000;

    build_infrastructure["build-infrastructure module"]
    style build_infrastructure stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px,color:#000;

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

## Status

ACCEPTED

## 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 author, test, publish and host the documentation.

## Status

PROPOSED

## Consequences