assertNull(exception.getMessage());
        assertNull(exception.getCause());
    }

    @Test
    public void test_constructor_withNullMessageAndCause() {
        // Test constructor with null message but valid cause
        Exception cause = new IllegalArgumentException("Invalid argument");
        DictionaryException exception = new DictionaryException(null, cause);

        assertNotNull(exception);

            linkElement.appendChild(classNameElement);
            return linkElement;
        }

        //this if is a bit cheesy but 1-letter classname surely means a generic type and the warning will be useless
        if (className.length() > 1) {
            listener.warning(String.format("Could not generate link for unknown class '%s'", className));
        }

        int statusCode = response.getStatusCode();
        // Accept either 200 (success) or other status codes based on implementation
        assertTrue(statusCode == 200 || statusCode == 400, "Status code should be 200 or 400, but was " + statusCode);

        if (statusCode == 200) {
            JsonPath jsonPath = JsonPath.from(response.asString());
            assertEquals(Integer.valueOf(0), jsonPath.get("response.status"));
        }
    }

                .when()
                .put(getApiPath() + "/upload");

        int statusCode = response.getStatusCode();
        assertTrue(statusCode == 200 || statusCode == 400, "Status code should be 200 or 400, but was " + statusCode);

        if (statusCode == 200) {
            JsonPath jsonPath = JsonPath.from(response.asString());
            assertEquals(Integer.valueOf(0), jsonPath.get("response.status"));
        }
    }

import java.util.stream.*;

/**
 * See https://github.com/gradle/gradle-private/issues/3919
 *
 * When merging `releaseX` branch into `master`, we should only use the release note from the `master` branch,
 * but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *

        emptyGenerator.addCondition("field1", "pattern2");
        emptyGenerator.addCondition("field2", "pattern.*");

        // We can't test isTarget properly without container,
        // but we can verify conditions are added
        assertNotNull(emptyGenerator);

        // Test that multiple conditions can be added without errors
        emptyGenerator.addCondition("type", "document");

## How the configuration works

We use Kotlin portable DSL to store TeamCity configuration, which means you can easily create a new pipeline
based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create
and test another isolated pipeline from any branch. 

We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`

            requiresNotSharedHost()
        }

    /*
     To avoid unnecessary rerun, what we do here is a bit complicated:

     1. Build a Gradle distribution with a fixed timestamp and hash it, but never use this distribution.
     2. Build a Gradle distribution with this hash as a version + fixed timestamp -> dogfood-first

A "build session" represents a single invocation of Gradle, for example when you run `gradlew build`.
A session runs the build one or more times.
For example, when continuous build is enabled, the session may run the build many times, but when it is disabled, the session will run the build once only.

The build session state is managed by the `BuildSessionState` class.

        setupPluginRequirements()
    }

    /**
     * Create projects and files required for plugins applied to the project (including transitively applied plugins).
     * These files are not required to run the task itself, but are required to apply the binary-compatibility plugin.
     */
    protected
    fun setupPluginRequirements() {
        projectDir.resolve("version.txt").writeText("9999999.0") // All released versions should be lower than this