use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a

4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.
5. The daemon sends the result back. For some requests, this might be a simple success/failure result, and for others this might also include a more complex object, such as a tooling API model.

The Wrapper then downloads the Gradle distribution (if necessary), starts the Launcher and runs the build, spawning and connecting to other processes such as the Daemon as required.

Embedding a Java runtime in the distribution would provide some benefits, such as allowing the Launcher, Daemon and Workers to run on it, removing the prerequisite of an installed Java runtime.

There are several different types of requests, such as a request to run a set of tasks, or to query a tooling model, or to stop.
Some requests will require that the build is configured and maybe some work executed, and other requests might not.

See [Build execution model](build-execution-model.md) for more details.

### Build state model

As Gradle executes, it acts on various pieces of the build definition, such as each project in the build.

 */
package org.codelibs.fess.sso;

/**
 * Represents the type of SSO (Single Sign-On) response being requested.
 * This enum is used to differentiate between various SSO operations,
 * such as metadata requests and logout actions.
 */
public enum SsoResponseType {
    /**
     * Indicates a request for SSO metadata, which is typically used for
     * configuration and discovery in protocols like SAML.
     */

 */
package org.codelibs.fess.exception;

/**
 * System exception class for the Fess search engine.
 * This exception is thrown when system-level errors occur in the Fess application,
 * such as configuration errors, initialization failures, or critical runtime issues.
 */
public class FessSystemException extends RuntimeException {

    /** Serial version UID for serialization compatibility */

 * of SSO authentication and authorization processes. It extends FessSystemException
 * to provide consistent error handling within the Fess system for SSO-related
 * processing failures such as token validation errors, communication failures
 * with SSO providers, or configuration issues.
 */
public class SsoProcessException extends FessSystemException {

    private static final long serialVersionUID = 1L;

 */
package org.codelibs.fess.dict;

/**
 * Abstract base class for all dictionary items in the Fess search system.
 * Dictionary items are used to store entries in various dictionaries such as
 * synonyms, kuromoji, protwords, and stopwords dictionaries.
 *
 */
public abstract class DictionaryItem {
    /** The unique identifier for this dictionary item */
    protected long id;

    /**

# ADR-0005 - Introduce a UI architecture module to the core platform

## Status

- ACCEPTED on 2024-02-07

## Context

The Gradle core platform provides many services to the Gradle platforms and builds logic. One such group of services allows logic to interact with the build user, to provide diagnostics, progress information, prompt for questions, and so on. Currently, these services are part of the core platform runtime architecture module.

Java serialization tends to produce larger serialized objects because it includes class metadata and other overhead.

- **Flexibility and Control:**
Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully.

- **Security:**
Java serialization poses security risks, especially related to deserialization vulnerabilities.