}.also { expected ->
      when (expected) {
        is SSLHandshakeException -> {
          // JDK 11+
        }

        is SSLException -> {
          // javax.net.ssl.SSLException: readRecord
        }

        is SocketException -> {
          // Conscrypt, JDK 8 (>= 292), JDK 9
        }

        else -> {
          assertThat(expected.message).isEqualTo("exhausted all routes")

   * Returns the {@link Method} instance for {@link #testAddAll_nullUnsupported()} so that tests can
   * suppress it with {@code FeatureSpecificTestSuiteBuilder.suppressing()} until <a
   * href="https://bugs.openjdk.org/browse/JDK-5045147">JDK-5045147</a> is fixed.
   */
  @J2ktIncompatible
  @GwtIncompatible // reflection
  public static Method getAddAllNullUnsupportedMethod() {

      ],
      "allowedVersions": "<10.0",
      "description": "JDK 11 requirement"
    },
    {
      "extends": [
        "monorepo:junit5"
      ],
      "allowedVersions": "<5.14.0",
    },
    {
      "matchPackageNames": [
        "org.junit-pioneer:junit-pioneer"
      ],
      "allowedVersions": "<2.0.0",
      "description": "JDK 11 requirement"
    },
    {
      "matchPackageNames": [

         * created TypeVariable will not interoperate with any JDK TypeVariable. But this is OK: We
         * don't _want_ our new TypeVariable to be equal to the JDK TypeVariable because it has
         * _different bounds_ than the JDK TypeVariable. And it wouldn't make sense for our new
         * TypeVariable to be equal to any _other_ JDK TypeVariable, either, because any other JDK

                t.setTargetCompatibility(JavaVersion.VERSION_14.getMajorVersion());
            }
            t.setBundledSignatures(Set.of("jdk-unsafe", "jdk-deprecated", "jdk-non-portable", "jdk-system-out"));
            t.setSignaturesFiles(
                project.files(resourcesDir.resolve("forbidden/jdk-signatures.txt"), resourcesDir.resolve("forbidden/es-all-signatures.txt"))
            );

          github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-windows-sample
          cancel-builds-on-update: true
          # We've removed the no-jdk distribution on master as well
          black-list-target-branches:
            - master
            - 6.8
          excluded-regions:
            - ^docs/.*
          black-list-labels:
            - '>test-mute'

com.sun.org.glassfish.**
com.sun.pisces.**
com.sun.prism.**
com.sun.proxy.**
com.sun.scenario.**
com.sun.t2k.**
com.sun.webkit.**
com.sun.xml.internal.**
jdk.internal.**
jdk.management.resource.internal.**
jdk.nashorn.internal.**
jdk.nashorn.tools.**
oracle.jrockit.jfr.**
org.jcp.xml.dsig.internal.**

[
  {
    "name": "kotlin.internal.jdk8.JDK8PlatformImplementations",
    "allDeclaredConstructors":true
  },
  {
    "name": "kotlin.KotlinVersion",
    "allPublicMethods": true,
    "allDeclaredFields":true,
    "allDeclaredMethods":true,
    "allDeclaredConstructors":true
  },
  {
    "name": "kotlin.KotlinVersion[]"
  },
  {
    "name": "kotlin.KotlinVersion$Companion"
  },
  {

          github-hooks: true
          status-context: elasticsearch-ci/packaging-tests-windows
          cancel-builds-on-update: true
          # We've removed the no-jdk distribution on master as well
          black-list-target-branches:
            - master
            - 6.8
          excluded-regions:
            - ^docs/.*
          white-list-labels:

    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
    and without configuring every plugin that require path to JDK tools.</p>

    @see <a href="/guides/mini/guide-using-toolchains.html">Guide to Using Toolchains</a>