* Google Docs is not a "code-oriented" tool, like Markdown can be
* Review in Google Docs is not as simple as a PR code review in GitHub

## Decision

The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.

The main logic with ADRs is to describe (architectural) decisions made:

            propertyName to propertyValue
        }
    }.toMap()

/**
 * Creates a [Provider] that returns `true` when this [Provider] has a value
 * and `false` otherwise. The returned [Provider] always has a value.
 * @see Provider.isPresent
 */
private
fun <T : Any> Provider<T>.presence(): Provider<Boolean> =
    map { true }.orElse(false)

     * to run on, by definition. All modules that this module depends on will
     * then be required to also support these target runtimes.
     *
     * The required runtimes for a project should be set if that project has
     * specific runtime requirements. For example, they must be able to run in
     * a worker (a compiler worker, test worker, worker API worker action),
     * or must be able to run in a client (TAPI model, TAPI client, CLI client).

     */
    protected void insertLogin(final Object member) {
        // nothing
    }

    /**
     * Checks if the current user has permission to access the given resource.
     * For admin actions, verifies that the user has appropriate admin roles or
     * meets the secured annotation requirements.
     *
     * @param resource the login handling resource to check permission for

        validator.initialize(annotation);
        // Test that initialization completes without exception
    }

    @Test
    public void test_classStructure() {
        // Test that the class exists and has the expected structure
        assertEquals("CustomSizeValidator should be in correct package", "org.codelibs.fess.validation.CustomSizeValidator",
                CustomSizeValidator.class.getName());

## Context

In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc.
Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:

- **Performance:**
Java's built-in serialization mechanism is often slower compared to other serialization solutions.
This is due to Java's use of reflection and the need to maintain a lot of metadata.

            task.getDestinationDirectory().convention(dslReference.getStagingRoot().dir("dsl"));
        });

        extension.dslReference(dslRef -> {
            // DSL ref has custom javascript
            ConfigurableFileTree js = objects.fileTree();
            js.from(dslReference.getRoot());
            js.include("*.js");
            dslRef.getResources().from(js);

/**
 * 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.
 */
fun <T: Any> atMostOneOf(vararg providers: Provider<T>): Provider<T> {
    return providers.map { provider ->
        provider.map {

        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());
    }

    @Test
    public void test_serialization() {
        // Test that the exception has serialVersionUID defined
        String message = "Serialization test";
        SearchEngineClientException exception = new SearchEngineClientException(message);

        <module name="UnusedImports"/>
        <module name="IllegalImport">
            <!--
                We shouldn't use jdk.internal types.

                com.beust and org.testng.collections has classes that look like Guava.
            -->
            <property name="illegalPkgs" value="jdk.internal,com.beust,org.testng.collections"/>
            <!--
                We prefer org.jspecify for nullability annotations.