Historically, Gradle has shipped with some Groovy types in very prominent APIs.
This required the Kotlin DSL to add special integration to work with Groovy closures.
This has also forced plugins written in languages other than Groovy to use Groovy types for some APIs.

When the Kotlin DSL was introduced, we made an effort to add non-Groovy equivalents for all APIs.

    * Com <a href="https://strawberry.rocks/docs/integrations/fastapi" class="external-link" target="_blank">docs para FastAPI</a>
* <a href="https://ariadnegraphql.org/" class="external-link" target="_blank">Ariadne</a>
    * Com <a href="https://ariadnegraphql.org/docs/fastapi-integration" class="external-link" target="_blank">docs para FastAPI</a>

 * <p>
 * Example usage:
 * <pre>
 * public class CustomPathScopeProvider implements PathScopeProvider {
 *     public Collection&lt;PathScope&gt; provides() {
 *         return Collections.singleton(pathScope("integration-test",
 *                 ProjectScope.TEST, DependencyScope.TEST));
 *     }
 * }
 * </pre>
 *
 * @see org.apache.maven.api.PathScope
 * @see org.apache.maven.api.spi.ExtensibleEnumProvider
 * @since 4.0.0

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-clean-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-deploy-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-jar-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>

import org.dbflute.optional.OptionalEntity;

import jakarta.annotation.Resource;

/**
 * Service class for managing group operations in the Fess application.
 * Provides CRUD operations for groups, including integration with LDAP manager
 * and user-group relationships. Handles group pagination, searching, and
 * maintaining data consistency between groups and associated users.
 */
public class GroupService {

    private long sequenceNumber;
    private int returnCode;
    
    public boolean isSuccess() { return returnCode == 0; }
    // Getters and setters...
}
```

## 5. Integration with Existing Code

### 5.1 Session Integration
```java
// In SmbSession.java
private WitnessClient witnessClient;
private boolean witnessEnabled;

public void initializeWitnessSupport() {

            } else {
                configurations["${prefix}TestDistributionRuntimeClasspath"].getSingleFileProvider()
            }
        )
        // Set the base user home dir to be share by integration tests.
        // The actual user home dir will be a subfolder using the name of the distribution.
        gradleUserHomeDir = intTestHomeDir

* **Keine Kompromisse** bei Datenbanken, Frontends, usw., sondern einfache Integration mit allen.

### Unbegrenzte Erweiterungen { #unlimited-plug-ins }

Oder mit anderen Worten, sie werden nicht benötigt. Importieren und nutzen Sie den Code, den Sie brauchen.