- 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.
This capability could help increase Gradle adoption outside of the JVM ecosystem.

Gradle can be invoked in different ways:

 */
public class JobProcess {
    /**
     * The underlying system process.
     */
    protected Process process;

    /**
     * The thread that handles reading from the process input stream.
     */
    protected InputStreamThread inputStreamThread;

    /**
     * Constructs a new JobProcess with the specified process.
     * Uses the default buffer size and no output callback.

        @Override
        public String getRealPath(String path) {
            if (path == null) {
                return tempDir.getAbsolutePath();
            }
            // Remove leading slash if present
            if (path.startsWith("/")) {
                path = path.substring(1);
            }
            return new File(tempDir, path.replace("/", File.separator)).getAbsolutePath();
        }

        return "ElevateWord [labelTypeIds=" + Arrays.toString(labelTypeIds) + ", labelTypeList=" + labelTypeList + ", boost=" + boost
                + ", createdBy=" + createdBy + ", createdTime=" + createdTime + ", reading=" + reading + ", suggestWord=" + suggestWord
                + ", updatedBy=" + updatedBy + ", updatedTime=" + updatedTime + ", docMeta=" + docMeta + "]";
    }

Java serialization is inherently Java-centric and does not support cross-language scenarios well.

- **Type Safety:**
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.

## Decision

We do not use Java serialization.
Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized.

/**
 * Job for purging expired documents from the search index.
 * This job removes documents that have passed their expiration time based on the expires field.
 * It helps maintain the search index by cleaning up outdated content automatically.
 */
public class PurgeDocJob {

    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(PurgeDocJob.class);

    /**

            "type" : "keyword"
          },
          "createdTime" : {
            "type" : "long"
          },
          "permissions" : {
            "type" : "keyword"
          },
          "reading" : {
            "type" : "keyword"
          },
          "suggestWord" : {
            "type" : "keyword"
          },
          "updatedBy" : {
            "type" : "keyword"
          },

    protected abstract Property<Integer> getPort();

    @Nested
    protected abstract Property<JavaLauncher> getJavaLauncher();

    @TaskAction
    public void startApplication() {
        System.out.println("serving docs at http://localhost:" + getPort().get());
        DeploymentRegistry registry = getDeploymentRegistry();
        JavaApplicationHandle handle = registry.get(getPath(), JavaApplicationHandle.class);
        if (handle == null) {

                                    <tr>
                                        <th><la:message key="labels.dict_kuromoji_reading"/></th>
                                        <td>${f:h(reading)}<la:hidden property="reading"/></td>
                                    </tr>
                                    <tr>
                                        <th><la:message key="labels.dict_kuromoji_pos"/></th>

 * size and makes us more conscious of which parts of a library we really need.
 *
 * WARNING: if you decide to do the minification by hand, make sure that you cover all paths of loading classes:
 * reflection, dynamic loading, etc. and understand how the library works internally.
 * These changes might break things in subtle ways otherwise.
 */
val keepPatterns = mapOf(
    "it.unimi.dsi:fastutil" to setOf(