// If we don't clean that up there might be leftover json files from other report builds running on the same machine.
                                    """
                                    results/performance/build/test-results-*.zip!performance-tests/report/css/*.css => $performanceResultsDir/

 *
 * Current implementation extracts these from the wrapper's API jars.
 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *

        )
        applyRule<DependencyRemovalByNameRule>("cglib:cglib", setOf("ant"))

        // We do not support running junit from Ant. Don't bundle ant-junit.
        applyRule<DependencyRemovalByNameRule>("org.apache.groovy:groovy-ant", setOf("ant-junit"))

        // GCS transitively depends on commons-logging.

You also need to run `mvn clean verify` with Java 8 before committing changes.

If you have ktlint errors, you can automatically fix them by running `mvn com.github.gantsign.maven:ktlint-maven-plugin:1.1.1:format`.

## How the configuration works

We use Kotlin portable DSL to store TeamCity configuration, which means you can easily create a new pipeline

        setStartTime(ComponentUtil.getSystemHelper().getCurrentTimeAsLong());
        setLastUpdated(ComponentUtil.getSystemHelper().getCurrentTimeAsLong());
        setJobStatus(Constants.RUNNING);
        final String myName = ComponentUtil.getFessConfig().getSchedulerTargetName();
        setTarget(StringUtil.isNotBlank(myName) ? myName : Constants.DEFAULT_JOB_TARGET);
    }

                                                        </c:when>
                                                        <c:when test="${data.jobStatus == 'running'}">
																		<span class="badge bg-success"><la:message
                                                                                key="labels.joblog_status_running"/></span>

### Generate Source Code

    $ mvn dbflute:download # (one time command)
    $ mvn dbflute:freegen
    $ mvn license:format

### Integration Tests

Integration tests require a running Fess server with OpenSearch. Follow these steps:

#### 1. Build Fess

    $ mvn antrun:run  # Download OpenSearch plugins (if not done)
    $ mvn package     # Build the package

#### 2. Start Fess Server

import org.junit.jupiter.api.io.TempDir
import java.io.File


@EnabledIfEnvironmentVariable(named = "CI", matches = ".*", disabledReason = "Tests rely on setup conditional on CI in gradlebuild.ci-reporting plugin running first, these test should only run if CI env var is present (it's value doesn't matter)")
class TestFilesCleanupServiceTest {
    @TempDir
    lateinit var projectDir: File

    @TempDir
    lateinit var testKitDir: File

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.

labels.scheduledjob_scriptType=Execution Method
labels.scheduledjob_scriptData=Script
labels.scheduledjob_jobLogging=Logging
labels.scheduledjob_crawler=Crawler Job
labels.scheduledjob_running=Running
labels.scheduledjob_active=Active
labels.scheduledjob_nojob=Disabled
labels.scheduledjob_button_start=Start Now
labels.scheduledjob_button_stop=Stop
labels.joblog_button_back=Back
labels.joblog_button_delete=Delete