* Be careful when using features introduced in Java 1.7 or later. Some parts of Gradle still need to run on Java 6.
* Normalize file paths in tests. The `org.gradle.util.internal.TextUtil` class has some useful functions for this purpose.

You can consult the [Architecture documentation](architecture) to learn about some of the architecture of Gradle.

### Contributing to documentation

# -*- mode: yaml -*-
manifest:
  version: 1.0

# The `automations` section lists automations to run on PRs in this repository.
# Each automation has an `if` key that defines conditions to run the automation,
# as well as a `run` key with the actions to do. All the conditions need to be true
# for the actions to run (there is an implicit AND relation between
# the conditions on each line).  Each condition is specified as a Jinja expression.  You

            "successful-report/build/tmp/teŝt files",
            "failed-test-with-leftover/build/tmp/teŝt files"
        )
    }

    @Test
    fun `build does not fail if a flaky test has leftover files`() {
        val result = run(":flaky-test-with-leftover:test", "--no-watch-fs").build()

        // leftover files failed tests are reported but not counted as an exception, but cleaned up eventually

        daemon --> worker

        worker2["Worker process"]
        daemon --> worker2

        worker3["Worker process"]
        daemon --> worker3
    
```

These are all Java processes. Each process has a corresponding "runtime".
All source code in Gradle is written to target one or more of these runtimes.

/**
 * A test that provides an IDE as environment for checking IDE and Gradle behavior during synchronization process.
 * These tests are running using `forking` executor, since current Gradle distribution has to be used as a Gradle version for IDE.
 */
@CacheableTask
abstract class SmokeIdeTest : DistributionTest() {
    override val prefix: String = "smokeIde"

 * @example {{ owners | byPlatform }}
 */
function byPlatform(files) {
    const result = new Map();
    files.forEach(file => {
        const platform = getPlatform(file);
        if (!result.has(platform)) {
            result.set(platform, []);
        }
        result.get(platform).push(file);
    });

    console.log("byPlatform: ");
    [...result.keys()].forEach(platform => {

    ],

    // starting
    [
        // there will be no leading '/'
        //   (which has been replaced by section "leading slash")
        // If starts with '**', adding a '^' to the regular expression also works
        /^(?=[^^])/,
        function startingReplacer () {
            // If has a slash `/` at the beginning or middle
            return !/\/(?!$)/.test(this)
                // > Prior to 2.22.1

# -*- mode: yaml -*-
manifest:
  version: 1.0

# The `automations` section lists automations to run on PRs in this repository.
# Each automation has an `if` key that defines conditions to run the automation,
# as well as a `run` key with the actions to do. All the conditions need to be true
# for the actions to run (there is an implicit AND relation between
# the conditions on each line).  Each condition is specified as a Jinja expression.  You

import org.gradle.api.tasks.PathSensitivity


/**
 * Verifies the correct behavior of a feature, as opposed to just a small unit of code.
 * Usually referred to as 'functional tests' in literature, but our code base has historically
 * been using the term 'integration test'.
 */
@CacheableTask
abstract class IntegrationTest : DistributionTest() {

    override val prefix = if (name.contains("CrossVersion")) "crossVersion" else "integ"

    def format = new SimpleDateFormat('yyyyMMddHHmmssZ')

    @TempDir
    File tmpDir

    def setup() {
        format.timeZone = TimeZone.getTimeZone("UTC")
    }

    def "updated released version file has expected format"() {
        given:
        def releasedVersionsFile = new File(tmpDir, "released-versions.json")
        releasedVersionsFile << '''{
  "latestReleaseSnapshot": {
    "version": "6.6-20200702230251+0000",