indexer.thread.dump.enabled=true
# Maximum number of unprocessed documents for the indexer.
indexer.unprocessed.document.size=1000
# Whether to enable click count tracking in the indexer.
indexer.click.count.enabled=true
# Whether to enable favorite count tracking in the indexer.
indexer.favorite.count.enabled=true
# Commit margin time (ms) for webfs in the indexer.
indexer.webfs.commit.margin.time=5000

NOTE: Due to the project size, the very first import can take a while and IntelliJ might become unresponsive for several seconds during this period.

IntelliJ automatically hides stacktrace elements from the `org.gradle` package, which makes running/debugging tests more difficult. You can disable this behavior by changing IntelliJ Preferences under Editor -> General -> Console. In the "Fold lines that contain" section, remove the `org.gradle` entry.

      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,

        project.findProperty("currentReleasedVersionBuildTimestamp").toString()
    )
}

val updateAgpVersions = tasks.register<UpdateAgpVersions>("updateAgpVersions") {
    comment = " Generated - Update by running `./gradlew updateAgpVersions`"
    currentGradleVersion = gradleModule.identity.version
    propertiesFile = layout.projectDirectory.file("gradle/dependency-management/agp-versions.properties")

# ADR-0007 - Support running Gradle on multiple Java versions and do not embed a Java runtime in the Gradle distribution

## Status

- PROPOSED on 2024-12-20

## Context

### Embedding a Java runtime in the Gradle distribution

There have been discussions on embedding a Java runtime in the Gradle distribution.
This would allow users to run Gradle without having to install a Java runtime beforehand.

If the intention is to gather user feedback on an early prototype, then the experimental property should be used.
If the intention is to allow an issue reporter to get additional local diagnostics when running a build in their proprietary environment, then the internal property is sufficient.

Examples of properties that follow the naming rules:

* `org.gradle.experimental.declarative-common`

          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "base-services",
          "build-cache",
          "flow-services",
          "input-tracking",
          "internal-integ-testing",
          "model-core",
          "persistent-cache",
          "process-memory-services",
          "scala",
          "snapshots",

        original.put("status", "running");
        original.put("createdTime", 1234567890L);

        final String json = coordinatorHelper.toJson(original);
        final Map<String, Object> parsed = coordinatorHelper.parseJson(json);

        assertEquals("operation", parsed.get("type"));
        assertEquals("reindex", parsed.get("name"));
        assertEquals("running", parsed.get("status"));

mvn clean install -DskipTests               # Then revert packaging back to war

# Integration tests (*Tests.java) - requires running Fess server
mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201"
```

### Running
```bash
./bin/fess              # From command line
# Or run org.codelibs.fess.FessBoot from IDE

            private final Map<String, String> infoMap = new HashMap<>();

            @Override
            public void store(String sessionId, boolean running) {
                // Track the final status
                if (!running) {
                    statusMap.put(Constants.CRAWLER_STATUS, Constants.F.toString());
                }
            }

            @Override