* <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

        <![CDATA[
      If false, flags the system to skip prompting the user for any information, or holding up the build
      waiting for any input.

      NOTE: It's also possible to switch to batch (i.e. non-interactive) mode using the '-B' command-line option.
    ]]></description>
    </expression>
  </expressions>

  <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>

---

## Architecture

### Module Structure

```
fess-crawler-parent/
├── fess-crawler/              # Core framework
├── fess-crawler-lasta/        # LastaFlute DI integration
└── fess-crawler-opensearch/   # OpenSearch backend
```

### Key Design Patterns

**Factory**: `CrawlerClientFactory`, `ExtractorFactory` - protocol/format-specific component selection

                result.projectSettingsPath = shellContext.projectSettingsPath;
                result.userSettingsPath = shellContext.userSettingsPath;
                result.interactive = shellContext.interactive;
                result.localRepositoryPath = shellContext.localRepositoryPath;
                result.effectiveSettings = shellContext.effectiveSettings;

- CLI client. This is the `gradle` or `gradlew` command, and is responsible for locating, starting and interacting with the Gradle daemon, potentially downloading the Gradle distribution. 
- Tooling API client. This a library that is embedded into applications, such as IDEs or CI agents, that allows them to act as a Gradle client.

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 {

    throwable.printStackTrace(new PrintWriter(stringWriter));
    return stringWriter.toString();
  }

  /**
   * Returns the stack trace of {@code throwable}, possibly providing slower iteration over the full
   * trace but faster iteration over parts of the trace. Here, "slower" and "faster" are defined in
   * comparison to the normal way to access the stack trace, {@link Throwable#getStackTrace()