}
            param("credentialsStorageType", "credentialsJSON")
            // Disallow Web UI changes to TeamCity settings
            param("teamcity.ui.settings.readOnly", "true")
            // Avoid rebuilding same revision if it's already built on another branch
            param("teamcity.vcsTrigger.runBuildOnSameRevisionInEveryBranch", "false")

### Build errors after regeneration

- Check property file syntax (no unescaped special characters)
- Ensure all property values are properly escaped
- Run `mvn clean` before rebuilding

## Additional Resources

- Fess Configuration: `src/main/resources/fess_config.properties`
- DBFlute FreeGen Configuration: `dbflute_fess/dfprop/lastafluteMap.dfprop`

     * atomically switches aliases, then cleans up old and backup indices.
     *
     * @param loadBulkData    whether to load default bulk data after rebuilding (using OpType.CREATE to skip existing documents)
     * @param targetPrefixes  the set of index prefixes to rebuild (e.g., "fess_config", "fess_user", "fess_log")

}

includeBuild("../build-logic-settings")

// Shared basics for all
include("basics")

// Platform: defines shared dependency versions
include("build-platform")

// Compute the identity/version we are building and related details (like current git commit)
include("module-identity")

// Code quality rules common to :build-logic and the root build
include("code-quality-rules")

// Plugins to build :build-logic plugins

# This workflow will build a Java project with Maven
# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven

name: Java CI with Maven

on:
  push:
    branches:
    - master
    - "*.x"
  pull_request:
    branches:
    - master
    - "*.x"
  workflow_dispatch:

jobs:
  build:
    runs-on: ubuntu-24.04
    env:
      PARENT_BRANCH: main

The build of Gradle enables the configuration cache by default as a dogfooding experiment.

Most tasks that are used to build Gradle support the configuration cache, but some don't. For example, building the documentation currently requires you to disable the configuration cache.

To disable the configuration cache, run the build with `--no-configuration-cache`.

        if (Constants.DEFAULT_FIELD.equals(field) && defaultField != null) {
            return defaultField;
        }
        return field;
    }

    /**
     * Functional interface for building query builders with field and boost parameters.
     */
    protected interface DefaultQueryBuilderFunction {
        /**
         * Applies the function to create a query builder for the specified field and boost.

    public void test_user_physicalDeliveryOfficeName() {
        final User user = new User();
        assertNull(user.getPhysicalDeliveryOfficeName());

        user.setPhysicalDeliveryOfficeName("Building A");
        assertEquals("Building A", user.getPhysicalDeliveryOfficeName());
    }

    @Test
    public void test_user_state() {
        final User user = new User();
        assertNull(user.getState());

            // Expected exception for empty field name
            assertTrue(e.getMessage().contains("field name is null or empty"));
        }

        // Assert deleteByQuery was NOT called due to exception in query building
        assertFalse(deleteByQueryCalled);
    }

    @Test
    public void test_execute_withOutOfMemoryError() {
        // Create mock SearchEngineClient that throws OutOfMemoryError

> For a comprehensive overview, please visit the [official Gradle project homepage](https://gradle.org).