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

                .collect(Collectors.joining(" "));
    }

    /**
     * Determines whether the current request is authorized to access the API endpoint.
     * This default implementation returns false, requiring subclasses to override
     * and implement proper access control logic.
     *
     * @return true if access is allowed, false otherwise
     */
    protected boolean isAccessAllowed() {
        return false;

     */
    public static NtlmAuthenticator getDefault() {
        return auth;
    }

    /**
     * Gets the URL that is requesting authentication.
     * @return the URL requiring authentication
     */
    protected final String getRequestingURL() {
        return this.url;
    }

    /**
     * Gets the authentication exception that triggered this request.

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

    @Test
    public void testRdmaConnectionLifecycle() throws Exception {
        // Test connection lifecycle without requiring real server
        RdmaProvider provider = RdmaProviderFactory.selectBestProvider();
        assertNotNull(provider, "Should always have a provider (at least TCP fallback)");

        // Use mock address for testing

        if (auth != null) {
            return;
        }
        auth = a;
    }

    /**
     * Gets the URL that is requesting authentication.
     * @return the URL requiring authentication
     */
    protected final String getRequestingURL() {
        return url;
    }

    /**
     * Gets the authentication exception that triggered this request.

     * if this source represents a resolved artifact with known coordinates.
     * <p>
     * This method is primarily used by resolved sources to provide the model ID
     * without requiring the XML to be parsed. For build sources, this typically
     * returns {@code null} since the coordinates are determined by parsing the POM.
     *

     */
    @Test
    void testWitnessEnvironmentConfiguration() throws Exception {
        // Test simulating real witness environment scenarios
        // This test validates integration patterns without requiring real cluster

        // Simulate witness service discovery
        InetAddress mockWitnessAddress = InetAddress.getByName("127.0.0.1");

        // Test witness client initialization patterns

 *   <li>network/transfer errors</li>
 *   <li>file system errors: permissions</li>
 * </ul>
 *
 * TODO carlos: all these possible has*Exceptions and get*Exceptions methods make the clients too
 *       complex requiring a long list of checks, need to create a parent/interface/encapsulation
 *       for the types of exceptions
 */
@Deprecated
public class ArtifactResolutionResult {
    private static final String LS = System.lineSeparator();

import jcifs.smb.SmbSessionInternal;
import jcifs.smb.SmbTransportInternal;

/**
 * Unit tests for SMB3 Multi-Channel functionality
 *
 * These tests verify the multi-channel implementation without requiring a real SMB server.
 */
@ExtendWith(MockitoExtension.class)
@MockitoSettings(strictness = Strictness.LENIENT)
class MultiChannelIntegrationTest {

    @Mock
    private SmbTransportInternal mockTransport;