However, this would limit the ability of the Gradle ecosystem plugin authors to take advantage of new Java features and improvements.

One example is when one of the most popular plugins started requiring Java 17 because the underlying framework behind the plugin began requiring 17, and code from the framework was used in the plugin itself.
What would have happened if Gradle was limited to _only Java 11_ at the time?

## Decision

            param("env.JDK8", javaHome(OpenJdk8, Os.LINUX))
            param("env.JDK11", javaHome(OpenJdk11, Os.LINUX))
            param("env.JDK17", javaHome(OpenJdk17, Os.LINUX))
            // Keep 21 and 25 for tests requiring it specifically: https://github.com/gradle/gradle/pull/35410#discussion_r2460835304
            param("env.JDK21", javaHome(OpenJdk21, Os.LINUX))
            param("env.JDK25", javaHome(OpenJdk25, Os.LINUX))

 *   <li>Streams include primitive-specialized variants such as {@code IntStream}, the use of which
 *       is strongly recommended.
 *   <li>Streams are standard Java, not requiring a third-party dependency (but requiring <a
 *       href="https://developer.android.com/studio/write/java8-support#library-desugaring">library
 *       desugaring</a> or <a

 *   <li>Setting {@code maven.consumer.pom.flatten=true} removes them during transformation</li>
 *   <li>Otherwise, an exception is thrown requiring one of the above options or manual mixin removal</li>
 * </ul>
 * <p>
 * <b>Dependency Filtering</b>: For non-POM projects with dependency management, the builder:
 * <ul>

 * which is commonly used for Kerberos-based authentication in Windows environments.
 * It handles the negotiation between client and server to establish a secure
 * authentication context without requiring users to explicitly enter credentials.
 *
 * The authenticator supports various configuration options including delegation,
 * basic authentication fallback, and localhost authentication bypass.
 */

  @Override
  /*
   * This suppression is here for two reasons:
   *
   * 1. b/192354773 in our checker affects toArray declarations.
   *
   * 2. `other[size] = null` is unsound. We could "fix" this by requiring callers to pass in an
   * array with a nullable element type. But probably they usually want an array with a non-nullable
   * type. That said, we could *accept* a `@Nullable T[]` (which, given that we treat arrays as

  @Override
  /*
   * This suppression is here for two reasons:
   *
   * 1. b/192354773 in our checker affects toArray declarations.
   *
   * 2. `other[size] = null` is unsound. We could "fix" this by requiring callers to pass in an
   * array with a nullable element type. But probably they usually want an array with a non-nullable
   * type. That said, we could *accept* a `@Nullable T[]` (which, given that we treat arrays as

 *     executor.execute(task);
 *   }
 * }
 * }
 *
 * <p>As another example, imagine that we produce a stream of data, and we want to cap it at 5kb per
 * second. This could be accomplished by requiring a permit per byte, and specifying a rate of 5000
 * permits per second:
 *
 * {@snippet :
 * final RateLimiter rateLimiter = RateLimiter.create(5000.0); // rate = 5000 permits per second
 * void submitPacket(byte[] packet) {

    //                                                                    ================

    /**
     * Testable subclass that bypasses ComponentUtil dependencies.
     * This allows testing the filter logic without requiring the DI container.
     */
    private static class TestableLoadControlFilter extends LoadControlFilter {
        private short cpuPercent = 0;
        private int webLoadControl = 0;

      Iterable<? extends ListenableFuture<? extends V>> futures) {
    return new FutureCombiner<>(false, ImmutableList.copyOf(futures));
  }

  /**
   * Creates a {@link FutureCombiner} requiring that all passed in futures are successful.
   *
   * <p>If any input fails, the returned future fails immediately.
   *
   * @since 20.0
   */
  @SafeVarargs