**For more information, please visit the [official project homepage](https://gradle.org)**

## Getting Started

### Cross-cutting architecture modules

There are some additional cross-cutting architecture modules that aren't themselves platforms:

#### Enterprise integration

Provides cross-cutting integration with Gradle's commercial product.

#### IDE integration

Provides cross-cutting integration with IDEs and other tooling.

#### Build infrastructure

## Cross-cutting architecture modules

There are some additional cross-cutting architecture modules that aren't platforms:

### Enterprise integration

Provides cross-cutting integration with Gradle's commercial product.

### IDE integration

Provides cross-cutting integration with IDEs and other tooling.

### Build infrastructure

platforms/core-execution/hashing/                           @gradle/bt-execution @gradle/bt-dv-build-cache
platforms/core-execution/snapshots/                         @gradle/bt-execution @gradle/bt-dv-build-cache

# Develocity integration
platforms/enterprise/                                   @gradle/bt-build-scan @gradle/ge-build-insights
platforms/enterprise/enterprise/                        @gradle/bt-build-scan @gradle/ge-testing @gradle/ge-build-insights @ldaley

Historically, Gradle has shipped with some Groovy types in very prominent APIs.
This required the Kotlin DSL to add special integration to work with Groovy closures.
This has also forced plugins written in languages other than Groovy to use Groovy types for some APIs.

When the Kotlin DSL was introduced, we made an effort to add non-Groovy equivalents for all APIs.

dependencies {
    implementation("gradlebuild:basics")

    implementation(project(":cleanup"))
    implementation(project(":documentation"))
    implementation(project(":integration-testing"))
    implementation(project(":performance-testing"))
    implementation(project(":profiling"))
    implementation(project(":binary-compatibility"))

    implementation("org.codenarc:CodeNarc") {

### Code change guidelines

All code contributions should contain the following:

* Create unit tests using [Spock](https://spockframework.org/spock/docs/2.0/index.html) for new classes or methods that you introduce.
* Create integration tests that exercise a Gradle build for the bug/feature. 
* Annotate tests that correspond to a bug on GitHub (`@Issue("https://github.com/gradle/gradle/issues/2622")`).