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

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

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

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

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

When sharing data with external tools, we use JSON.

## Status

ACCEPTED

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

    testImplementation(projectTests(":compiler:tests-common"))
    testApi(projectTests(":compiler:test-infrastructure-utils"))
    testApi(projectTests(":compiler:test-infrastructure"))
    testImplementation(projectTests(":compiler:tests-common-new"))
    testImplementation(projectTests(":compiler:fir:analysis-tests:legacy-fir-tests"))

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. 

# All directories that are not explicitly listed below are considered
# unassigned. This means that the ownership may be unknown, lost or
# mixed across several groups.
* @gradle/bt-unassigned-maintainers

# Build infrastructure
.teamcity/                                  @gradle/bt-developer-productivity
.github/                                    @gradle/bt-developer-productivity @gradle/bt-support # This might need to be more finegrained in the future

					"plugin-use",
					"native",
					"java-compiler-plugin",
					"file-temp",
					"concurrent",
					"functional",
					"test-suites-base",
					"internal-testing",
					"io",
					"testing-jvm-infrastructure",
					"cli"
				]
			},
			{
				"parallelizationMethod":{
					"name":"TestDistribution"
				},
				"subprojects":[
					"language-java",
					"build-cache-base",
					"normalization-java",