},
        "latvian_override": {
          "type":       "stemmer_override",
          "rules": []
        },
        "lithuanian_stop": {
          "type":       "stop",

        },
        "latvian_override": {
          "type":       "stemmer_override",
          "rules": []
        },
        "lithuanian_stop": {
          "type":       "stop",

# ADR-0006 - Use of Provider APIs in Gradle

## Status

- ACCEPTED on 2024-06-21

## Context

# ADR-0003 - Avoid introducing Groovy types to public API

## Status

- ACCEPTED on 2024-01-12

## Context

Gradle's public API requires equal access from all JVM-based languages.
Kotlin, Groovy, Java, and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library.

Historically, Gradle has shipped with some Groovy types in very prominent APIs.

        String[] fields = { "api1", "api2", "api1", "api3", "api2" };
        queryFieldConfig.setApiResponseFields(fields);

        // Set should contain unique values only
        assertEquals(3, queryFieldConfig.apiResponseFieldSet.size());
        assertTrue(queryFieldConfig.apiResponseFieldSet.contains("api1"));
        assertTrue(queryFieldConfig.apiResponseFieldSet.contains("api2"));

* **Consistency with dependencies**: Gradle's ecosystem and dependencies predominantly use American English

### Exceptions

Some legitimate exceptions exist where British English or other variants must be preserved:

* **Third-party APIs and libraries**: When integrating with external APIs that use different spelling conventions

import gradlebuild.basics.PublicKotlinDslApi;
import org.gradle.api.Plugin;
import org.gradle.api.Project;
import org.gradle.api.artifacts.Configuration;
import org.gradle.api.attributes.Category;
import org.gradle.api.attributes.DocsType;
import org.gradle.api.attributes.Usage;
import org.gradle.api.file.ConfigurableFileTree;
import org.gradle.api.file.ProjectLayout;
import org.gradle.api.model.ObjectFactory;

      When doing so, still annotate nullable parameters and the return type as `@Nullable`.
  * Do not use `@Contract` for public APIs.
  * For polynull public APIs, the solution has to be decided on a case-by-case basis.

Do not remove `null` checks on public API boundaries, even if the annotations (or rather lack of them) suggest this.
Not all client code is compiled with NullAway.

platforms/documentation/docs/src/docs/userguide/reference/dsl-apis/kotlin_dsl.adoc                          @gradle/bt-docs-reviewers @gradle/bt-tide
platforms/documentation/docs/src/docs/userguide/reference/dsl-apis/migrating_from_groovy_to_kotlin_dsl.adoc @gradle/bt-docs-reviewers @gradle/bt-tide

│   │   ├── admin/             # Admin controllers ({feature}/ with Action, Forms)
│   │   └── api/               # API controllers
│   ├── service/               # Business logic services
│   ├── pager/                 # Pagination handlers
│   └── job/                   # Background jobs
├── api/                       # REST API infrastructure
├── opensearch/                # DBFlute integration for OpenSearch