run it using Gradle:

-------------------------------------
./gradlew run
-------------------------------------

==== Launching and debugging from an IDE

If you want to run Elasticsearch from your IDE, the `./gradlew run` task
supports a remote debugging option:

---------------------------------------------------------------------------
./gradlew run --debug-jvm

When working on some source code it is important to be aware of the runtimes in which it will run, so that you don't break these constraints.
There is some assistance in the IDE for this plus a lot of validation that is applied at build time and on CI, but it is useful to keep these constraints in mind as well.

See [Gradle runtimes](runtimes.md) for a list of these runtimes and more details.

```

### Running
```bash
./bin/fess              # From command line
# Or run org.codelibs.fess.FessBoot from IDE
# Access: http://localhost:8080/ (Admin: admin/admin)
```

### Code Formatting
```bash
mvn formatter:format    # Format code
mvn license:format      # Add license headers
```

## Directory Structure

There are some additional cross-cutting architecture modules that aren't themselves platforms:

#### Enterprise integration

Provides cross-cutting integration with Gradle's commercial product.

#### IDE integration

Provides cross-cutting integration with IDEs and other tooling.

#### Build infrastructure

Provides build logic, libraries, test suites and infrastructure to support developing and releasing Gradle.

    </module>

    <!-- Forbid using '!' for logical negations in favour of checking against 'false' explicitly. -->
    <!-- This is only reported in the IDE for now because there are many violations -->
    <module name="DescendantToken">
        <property name="id" value="BooleanNegation" />
        <property name="tokens" value="EXPR"/>

            BuildResumptionDataRepository buildResumptionDataRepository,
            SuperPomProvider superPomProvider,
            DefaultSessionFactory defaultSessionFactory,
            @Nullable @Named("ide") WorkspaceReader ideWorkspaceReader) {
        this.lookup = lookup;
        this.eventCatapult = eventCatapult;
        this.legacySupport = legacySupport;
        this.sessionScope = sessionScope;

    "linux" : 562
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for Eclipse",
  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 999
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for IDEA",
  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 1018
  } ]

  }, {
    "testId" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for Eclipse",
    "groups" : [ {
      "testProject" : "largeJavaMultiProject",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.java.JavaIDEModelPerformanceTest.get IDE model for IDEA",
    "groups" : [ {
      "testProject" : "largeJavaMultiProject",

## Getting Started

Just run `gradlew -p benchmarks run` from the project root
directory. It will build all microbenchmarks, execute them and print
the result.

## Running Microbenchmarks

Running via an IDE is not supported as the results are meaningless
because we have no control over the JVM running the benchmarks.

If you want to run a specific benchmark class like, say,
`MemoryStatsBenchmark`, you can use `--args`:

```

            testTask.onlyIf(t -> isEnabled(project));
        });

        setupTestDependenciesDefaults(project, yamlCompatTestSourceSet);

        // setup IDE
        GradleUtils.setupIdeForTestSourceSet(project, yamlCompatTestSourceSet);

        // add a lifecycle task to allow for a possible future additional rest compatibility without needing to change task names