* Be careful when using features introduced in Java 9 or later. Some parts of Gradle still need to run on Java 8.
* 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.

The Wrapper then downloads the Gradle distribution (if necessary), starts the Launcher and runs the build, spawning and connecting to other processes such as the Daemon as required.

Embedding a Java runtime in the distribution would provide some benefits, such as allowing the Launcher, Daemon and Workers to run on it, removing the prerequisite of an installed Java runtime.

plugins {
    `kotlin-dsl`
}

group = "gradlebuild"

description = "Provides a plugin for publishing some of Gradle's subprojects to Artifactory or the Plugin Portal"

dependencies {
    implementation(projects.basics)
    implementation(projects.moduleIdentity)

    implementation(buildLibs.publishPlugin)

    }

    @Test
    public void test_crawlingInfoPager_clear() {
        final CrawlingInfoPager pager = new CrawlingInfoPager();
        pager.id = "some-id";
        pager.sessionId = "some-session";
        pager.setCurrentPageNumber(5);

        pager.clear();

        assertNull(pager.id);
        assertNull(pager.sessionId);
    }

    @Test

        assertProvideThrowsException("TestClassification");
        assertProvideThrowsException("NonExistent");
        assertProvideThrowsException("");
        assertProvideThrowsException("Some.Classification");
        assertProvideThrowsException("Project.TestClassification");
    }

    @Test
    public void test_provide_nullClassificationName() {
        // Test with null classification name
        try {

#### JVM platform

This is a platform that builds on the core and software platforms to add support for developing software that runs on the JVM.
This includes software that is implemented using Java, Kotlin or some other JVM language.

This platform provides specific support for Java, Groovy and Scala, and includes the foojay toolchain plugin. 

#### Extensibility platform

* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers
* Missing null checks may cause NullPointerException
* Bridging with Kotlin code is polluted with platform types
* Some public APIs have incorrect nullability annotations (both overly restrictive and overly permissive)

While there are competing ways to represent absence (`Optional`, "Null Object" pattern, method overloads),

    }

    @Test
    public void test_execute_withInvalidScriptType() {
        // Try to execute with non-existent script type
        try {
            scriptExecutor.execute("nonexistent", "some script");
            fail("Expected ScriptEngineException");
        } catch (ScriptEngineException e) {
            assertTrue(e.getMessage().contains("nonexistent"));
        }
    }

    @Test

    - uses: actions/setup-java@v5
      with:
        distribution: temurin
        java-version: 17
    - name: Setup Gradle
      uses: gradle/actions/dependency-submission@v6
      env:
        # Exclude some projects and configurations that should not contribute to the dependency graph
        DEPENDENCY_GRAPH_EXCLUDE_PROJECTS: ':docs|:internal-performance-testing|:enterprise-plugin-performance|:performance|:internal-integ-testing'

            thread.join(testDurationMs + 1000);
        }

        // Verify that alive was changed to false
        assertFalse("alive should be false after writer thread", dataStore.alive);

        // At least some observations from reader threads should have seen false
        // due to volatile ensuring visibility
        int falseCount = 0;
        for (int i = 0; i < readerThreadCount; i++) {