Repository navigation
Upgrade Gradle to 9.8.0 - #24
Merged
Merged
Conversation
- gradle/wrapper: distributionUrl bumped to 9.8.0; wrapper jar and gradlew.bat regenerated by `./gradlew wrapper --gradle-version 9.8.0 --distribution-type bin` (run twice). gradlew is unchanged. - gradle.properties: set org.gradle.tooling.parallel=true explicitly. Gradle 9.8 deprecates deriving Tooling API (IDE sync) model-building parallelism from org.gradle.parallel, and Gradle 10 makes it an error. true keeps the current behavior. - CI: actions/setup-java v5 -> v6, matching the xtclang/xvm baseline.
The XTC plugin (0.4.4-SNAPSHOT, xtclang/xvm#651) no longer redirects Java's processResources into build/xtc/main/resources. processXtcResources now copies the source set's resources on its own, and compileXtc reads only its output. - platformUI: processXtcResources copies the guiDistDir srcDir, so it must depend on buildGui. Without that, Gradle fails validation (implicit dependency on buildGui's output). - kernel: apply the platform.httpPort/httpsPort cfg.json filter to processXtcResources. On processResources the overrides only reached Java's unused output, so the compiled kernel module and the exported cfg.json kept the default ports (including in Docker builds, which set these properties).
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the Gradle wrapper from 9.7.1 to 9.8.0, following the same steps as #22/#23. It also adapts two build scripts to the current XTC plugin snapshot's separate resource output.
Gradle 9.8.0
gradle/wrapper/: distribution URL bumped togradle-9.8.0-bin.zip. Wrapper regenerated with./gradlew wrapper --gradle-version 9.8.0 --distribution-type bin, run twice. The jar's SHA-256 matches the published 9.8.0 wrapper checksum.gradlew.batpicks up Gradle 9.8's Windows start-script changes;gradlewis unchanged.gradle.properties: addsorg.gradle.tooling.parallel=true. Gradle 9.8 deprecates lettingorg.gradle.parallel=trueimplicitly enable parallel Tooling API model building, and Gradle 10 makes it an error. The warning only appears during IDE sync, never in a CLI build. I reproduced it by fetching project models through the Tooling API, and setting the property explicitly removes it.truekeeps today's behavior.actions/setup-javav5 → v6, matching xtclang/xvm and xtclang/examples. The v6 notes list no breaking changes for these inputs (temurin, Java 25). The other actions are already on their latest major versions.I went through the rest of the 9.7 → 9.8 upgrade guide: configuration-time process execution, enabling the build cache from build logic, StartParameter, signing, attribute types, Copy/Sync
destinationDiroverrides, task logging listeners, Kotlinobjectstate in the configuration cache, and toolchain paths. None of these apply to this build. TheDockerfileuses./gradlew, so it needs no change.XTC plugin resource change (not caused by Gradle 9.8)
The
0.4.4-SNAPSHOTplugin now includes xtclang/xvm#651. It no longer redirects Java'sprocessResourcesintobuild/xtc/main/resources.processXtcResourcescopies the source set's resources into its own output, andcompileXtcreads only that output.processXtcResourcesnow copies thegui/distsrcDir, so it needsdependsOn(buildGui)likeprocessResources. Without it, the build fails validation:Task ':platformUI:processXtcResources' uses this output of task ':platformUI:buildGui' without declaring an explicit or implicit dependency.platform.httpPort/platform.httpsPortcfg.jsonfilter moves fromprocessResourcestoprocessXtcResources. With the new plugin, the filter onprocessResourcesonly changes Java's unused output. The compiled kernel module and the exportedcfg.jsonsilently kept the default ports, including in Docker builds, which set these properties viaORG_GRADLE_PROJECT_*. With-Pplatform.httpPort=9999 -Pplatform.httpsPort=9443:build/xtc/main/resources/cfg.json→8080/8090build/xtc/main/resources/cfg.json→9999/9443settings.gradle.ktsresolvesorg.xtclangfrommavenLocal()first, so a stale local snapshot can mask this. I verified against the published snapshots with-Dmaven.repo.local=<empty dir>.Verification
Against the remote
0.4.4-SNAPSHOTplugin and XDK (-Dmaven.repo.local=<empty dir> --refresh-dependencies):./gradlew clean, then./gradlew build installDist --stacktrace --console=plain --warning-mode=all --no-build-cache --no-daemon: BUILD SUCCESSFUL, 50 tasks. No deprecation warnings and no problems reported.--warning-mode=all: no deprecation warnings.actionlint .github/workflows/ci.ymlpasses.