All source code in Gradle is written to target one or more of these runtimes.
Most source code targets the daemon and the remaining code either targets a single runtime, for example the Gradle client, or is shared across multiple runtimes.

## Composition by architecture modules

Each [architecture module and platform](platforms.md) can contribute code to any of the runtimes.

    protected boolean httpOnly = true;

    /**
     * Retrieves the user code for the current request.
     * The user code is used to uniquely identify users across sessions and requests.
     * It checks multiple sources in order: request attribute, request parameter, cookie, user bean, or generates a new one.
     *
     * @return the user code string, or null if no valid session exists
     */
    public String getUserCode() {

     *
     * @param doc The document.
     * @param code The script code.
     * @return The script.
     */
    public Script createScript(final Map<String, Object> doc, final String code) {
        final StringBuilder buf = new StringBuilder(100);
        buf.append(code);
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

        String result = markdownRenderer.render("Use `code` here");
        assertTrue(result.contains("<code>code</code>"));
    }

    @Test
    public void test_render_codeBlock() {
        String markdown = "```\ncode block\n```";
        String result = markdownRenderer.render(markdown);
        assertTrue(result.contains("<pre>"));
        assertTrue(result.contains("<code>"));
        assertTrue(result.contains("code block"));

    public abstract ConfigurableFileCollection getCssFiles();

    /**
     * The source code to be documented. This should be the "public" APIs.
     */
    public abstract ConfigurableFileCollection getDocumentedSource();

    /**
     * Source code root folders. Java, Groovy and Kotlin public API sources, including
     * generated code.
     */
    public abstract ConfigurableFileCollection getSourceRoots();

    /**

Each process, or "runtime", applies different constraints to the code that runs in that process.
For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.

                    session.removeAttribute(OIC_STATE);
                    final String code = request.getParameter("code");
                    final String reqState = request.getParameter("state");
                    if (logger.isDebugEnabled()) {
                        logger.debug("code: {}, state(request): {}, state(session): {}", code, reqState, sesState);
                    }

- ACCEPTED on 2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".

* They are not synced with the code to reflect the eventual solution that is committed
* 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

```

### 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

```
src/main/java/org/codelibs/fess/
├── FessBoot.java              # Application entry point