// Even though the contract in System.getProperties() specifies that a value will exist for
      // all of the listed keys, for some reason the "java.compiler" key returns null in some JVMs.
      if (property == JAVA_COMPILER) {
        continue;
      }
      // Removed in Java 9:
      // https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2C896CA8-927C-4381-A737-B1D81D964B7B

      // Even though the contract in System.getProperties() specifies that a value will exist for
      // all of the listed keys, for some reason the "java.compiler" key returns null in some JVMs.
      if (property == JAVA_COMPILER) {
        continue;
      }
      // Removed in Java 9:
      // https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2C896CA8-927C-4381-A737-B1D81D964B7B

        return "Unknown";
    }

    /**
     * Gets the instance ID for this Fess instance.
     * Combines scheduler.target.name (if configured), hostname, and PID
     * to ensure uniqueness across multiple JVMs on the same host.
     *
     * @return The instance ID.
     */
    public String getInstanceId() {
        final String targetName = ComponentUtil.getFessConfig().getSchedulerTargetName();

  // safely publish these objects and we won't need this whole discussion.
  // TODO(user,lukes): consider adding volatile to all these fields since in current known JVMs
  // that should resolve the issue. This comes at the cost of adding more write barriers to the
  // implementations.

  private Futures() {}

  /**

  alias(libs.plugins.jlink)
  alias(libs.plugins.extra.java.module.info)
}

dependencies {
  implementation(projects.okhttp)
  implementation(projects.loggingInterceptor)

  // Force version 26.0.2-1 which is a proper JPMS module, unlike transitive 13.0
  implementation(libs.jetbrains.annotations)

  testImplementation(projects.okhttp)
  testImplementation(projects.loggingInterceptor)
  testImplementation(projects.mockwebserver3)

 *  Fix: The previous release would crash when running on Robolectric. We didn't anticipate
    running our Android artifact on the JVM platform!


## Version 5.0.0-alpha.15

_2025-05-28_

**This release introduces separate JVM and Android artifacts.** Until now, we've distributed OkHttp
as a JVM library that _detects_ Android capabilities at runtime, but that doesn't offer

Yuri Schimke <******@****.***> 1770157079 +0000

Yuri Schimke <******@****.***> 1770648026 -0800

              files=".*[/\\]platforms[/\\]jvm[/\\]language-jvm[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]jvm[/\\]language-jvm[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]tasks[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-jvm",
    "path": "platforms/jvm/testing-jvm",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-jvm-infrastructure",
    "path": "platforms/jvm/testing-jvm-infrastructure",
    "unitTests": true,
    "functionalTests": false,