Bump Gradle to 9.4.0 by Eng-Fouad · Pull Request #52894 · quarkusio/quarkus

Eng-Fouad · 2026-03-04T11:04:52Z

This release adds support for Java 26.
Gradle 9.4.0 release notes: https://docs.gradle.org/9.4.0/release-notes.html

gsmet · 2026-03-04T17:10:34Z

Looks like something is wrong :)

Eng-Fouad · 2026-03-05T00:18:28Z

These 2 test cases:

quarkus/devtools/gradle/gradle-application-plugin/src/test/java/io/quarkus/gradle/tasks/TasksConfigurationCacheCompatibilityTest.java

Lines 69 to 82 in 98d9de6

    
           @ParameterizedTest 
        
           @Order(2) 
        
           @MethodSource("compatibleTasks") 
        
           public void configurationCacheIsReusedTest(String taskName) throws IOException, URISyntaxException { 
        
               URL url = getClass().getClassLoader().getResource("io/quarkus/gradle/tasks/configurationcache/main"); 
        
               FileUtils.copyDirectory(new File(url.toURI()), testProjectDir.toFile()); 
        
               FileUtils.copyFile(new File("../gradle.properties"), testProjectDir.resolve("gradle.properties").toFile()); 
        
               BuildResult firstBuild = buildResult(taskName, "--configuration-cache"); 
        
               assertTrue(firstBuild.getOutput().contains("Configuration cache entry stored")); 
        
               BuildResult secondBuild = buildResult(taskName, "--configuration-cache"); 
        
               assertTrue(secondBuild.getOutput().contains("Reusing configuration cache.")); 
        
           }

quarkus/devtools/gradle/gradle-application-plugin/src/test/java/io/quarkus/gradle/tasks/TasksConfigurationCacheCompatibilityTest.java

Lines 84 to 98 in 98d9de6

    
           @ParameterizedTest 
        
           @Order(3) 
        
           @MethodSource("compatibleTasks") 
        
           public void configurationCacheIsReusedWhenProjectIsolationIsUsedTest(String taskName) 
        
                   throws IOException, URISyntaxException { 
        
               URL url = getClass().getClassLoader().getResource("io/quarkus/gradle/tasks/configurationcache/main"); 
        
               FileUtils.copyDirectory(new File(url.toURI()), testProjectDir.toFile()); 
        
               FileUtils.copyFile(new File("../gradle.properties"), testProjectDir.resolve("gradle.properties").toFile()); 
        
               BuildResult firstBuild = buildResult(taskName, "-Dorg.gradle.unsafe.isolated-projects=true"); 
        
               assertTrue(firstBuild.getOutput().contains("Configuration cache entry stored")); 
        
               BuildResult secondBuild = buildResult(taskName, "-Dorg.gradle.unsafe.isolated-projects=true"); 
        
               assertTrue(secondBuild.getOutput().contains("Reusing configuration cache.")); 
        
           }

are failing at assertTrue(secondBuild.getOutput().contains("Reusing configuration cache."));.

I debugged content of secondBuild.getOutput() and I noticed this line:

Calculating task graph as configuration cache cannot be reused because system property 'idea.io.use.nio2' has changed.

Not sure how to fix it. cc @aloubyansky

This issue could be related: gradle/gradle#30145 cc @cdsap

cdsap · 2026-03-05T03:11:31Z

I can take a look at those tests, @Eng-Fouad. I’m not sure why 9.4 would break them, but I’ll dig in.

Also related: #52506

cdsap · 2026-03-05T23:20:58Z

I can reproduce the issue in Gradle 9.4.0 with a simple plugin like:

public class SystemPropertiesPlugin implements Plugin<Project> {

    @Override
    public void apply(Project project) {

        project.getTasks().register("foo", task -> {
            System.getProperties().forEach((key, value) -> {
            });
        });
    }
}

Note: it's only reproducible within the TestKit build.
I have pinged the Build Tool team and hope to have an answer tomorrow

cdsap · 2026-03-07T03:59:13Z

The Build Tool team investigated the issue. The test fails on the first run for all Gradle versions because the project directory path is randomized, which prevents cache hits and forces recompilation. This recompilation resets the compiler environment and changes the system property value.

With Gradle 9.4.0, the test continues to fail on subsequent runs as well, likely due to a side effect introduced in gradle/gradle#35692. When the project directory path is stable, the issue does not occur.

I've created this PR #52959 to workaround this issue

gsmet

I rebased the PR.

quarkus-bot · 2026-03-07T16:00:20Z

Status for workflow `Quarkus CI`

This is the status report for running Quarkus CI on commit dee05b9.

Failing Jobs

Status	Name	Step	Failures	Logs	Raw logs	Build scan
❌	JVM Tests - JDK 17	`Build`	Failures	Logs	Raw logs	🔍
❌	JVM Tests - JDK 21	`Build`	Failures	Logs	Raw logs	🔍
❌	JVM Tests - JDK 25	`Build`	Failures	Logs	Raw logs	🔍
❌	JVM Tests - JDK 25 Semeru	`Build`	Failures	Logs	Raw logs	🔍
❌	JVM Tests - JDK 17 Windows	`Build`	Failures	Logs	Raw logs	🔍
✔️	Gradle Tests - JDK 25			Logs	Raw logs	🔍
❌	Gradle Tests - JDK 17 Windows	`Build`	⚠️ Check →	Logs	Raw logs	🚧

You can consult the Develocity build scans.