Skip to content

Upgrade Gradle to 9.8.0 - #24

Merged
lagergren merged 2 commits into
masterfrom
gradle-9.8.0-upgrade
Oct 2, 2026
Merged

lagergren merged 2 commits into
masterfrom
gradle-9.8.0-upgrade

Conversation

@lagergren

Copy link
Copy Markdown
Contributor

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 to gradle-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.bat picks up Gradle 9.8's Windows start-script changes; gradlew is unchanged.
  • gradle.properties: adds org.gradle.tooling.parallel=true. Gradle 9.8 deprecates letting org.gradle.parallel=true implicitly 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. true keeps today's behavior.
  • CI: actions/setup-java v5 → 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 destinationDir overrides, task logging listeners, Kotlin object state in the configuration cache, and toolchain paths. None of these apply to this build. The Dockerfile uses ./gradlew, so it needs no change.

XTC plugin resource change (not caused by Gradle 9.8)

The 0.4.4-SNAPSHOT plugin now includes xtclang/xvm#651. It no longer redirects Java's processResources into build/xtc/main/resources. processXtcResources copies the source set's resources into its own output, and compileXtc reads only that output.

  • platformUI: processXtcResources now copies the gui/dist srcDir, so it needs dependsOn(buildGui) like processResources. Without it, the build fails validation: Task ':platformUI:processXtcResources' uses this output of task ':platformUI:buildGui' without declaring an explicit or implicit dependency.
  • kernel: the platform.httpPort/platform.httpsPort cfg.json filter moves from processResources to processXtcResources. With the new plugin, the filter on processResources only changes Java's unused output. The compiled kernel module and the exported cfg.json silently kept the default ports, including in Docker builds, which set these properties via ORG_GRADLE_PROJECT_*. With -Pplatform.httpPort=9999 -Pplatform.httpsPort=9443:
    • before: build/xtc/main/resources/cfg.json → 8080 / 8090
    • after: build/xtc/main/resources/cfg.json → 9999 / 9443

settings.gradle.kts resolves org.xtclang from mavenLocal() 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-SNAPSHOT plugin 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.
  • With each script fix reverted on its own, I saw the platformUI validation failure and the kernel default-port result above.
  • Tooling API model fetch (IDE-sync equivalent) with --warning-mode=all: no deprecation warnings.
  • actionlint .github/workflows/ci.yml passes.

- 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).
@lagergren
lagergren merged commit 8df5449 into master Oct 2, 2026
1 check passed
@lagergren
lagergren deleted the gradle-9.8.0-upgrade branch October 2, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant