"swedish_keywords",
            "swedish_override",
            "swedish_stemmer"
          ]
        },
        "thai_analyzer": {
          "type": "custom",
          "tokenizer": "thai",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "thai_stop",
            "thai_keywords"
          ]
        },

            "swedish_keywords",
            "swedish_override",
            "swedish_stemmer"
          ]
        },
        "thai_analyzer": {
          "type": "custom",
          "tokenizer": "thai",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "thai_stop",
            "thai_keywords"
          ]
        },
        "turkish_analyzer": {

            "swedish_keywords",
            "swedish_override",
            "swedish_stemmer"
          ]
        },
        "thai_analyzer": {
          "type": "custom",
          "tokenizer": "thai",
          "filter": [
            "truncate20_filter",
            "lowercase",
            "thai_stop",
            "thai_keywords"
          ]
        },
        "turkish_analyzer": {

## Decision

We do not introduce new public API methods that include Groovy types in their signatures.
Existing Groovy methods will not be removed immediately.

## Consequences

* If we would have used `Closure`, we must instead use `Action<T>`, `Spec<T>`, `Callable<T>`, or `Transformer<OUT, IN>`.
* We need to ensure all APIs that are exposed in the Groovy DSL go through runtime decoration.

While there are competing ways to represent absence (`Optional`, "Null Object" pattern, method overloads),
it is unlikely that we'll be able to remove `null` entirely.

After migrating to Java 8, we can use pluggable type checkers to ensure that our annotations are consistent, 
and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

new properties on a task, extension or domain object that use plain getters and setters.  It is also not acceptable to add setters that take a Provider.

Note that when adding a lazy property to an existing class, you need to check if instances of the class are instantiated via ObjectFactory. Most classes are instantiated this way, but it's possible that a class without any lazy properties was never updated to use it. A tell-tale sign that an object is not instantiated via the ObjectFactory...

        // This test verifies that printThreadDump() method exists and can be called without exceptions
        try {
            ThreadDumpUtil.printThreadDump();
        } catch (Exception e) {
            fail("printThreadDump() should not throw exceptions: " + e.getMessage());
        }
    }

    @Test
    public void test_printThreadDumpAsWarn() {

): GradleBuildStep =
    GradleBuildStep(init)
        .apply(custom)
        .also {
            step(it)
        }

/**
 * Adds a [Gradle build step](https://confluence.jetbrains.com/display/TCDL/Gradle)
 * that runs with the Gradle wrapper.
 *
 * @see GradleBuildStep
 */
fun BuildSteps.gradleWrapper(
    buildType: BuildType? = null,
    init: GradleBuildStep.() -> Unit,
): GradleBuildStep =
    customGradle(init) {

If you didn't sign off your commits before creating the pull request, you can fix that after the fact.

To sign off a single commit:

`git commit --amend --signoff`

    setOf(":docs:docsTest", "docs:docsTest")
        .any(gradle.startParameter.taskNames::contains)


/**
 * Returns a new provider that takes its value from at most one
 * of the given providers. If no input provider is present, the output
 * provider will not be present. If more than one input provider
 * has a value specified, the resulting provider will throw an
 * exception when queried.
 */