Skip to content

Fix/323#325

Merged
xzel23 merged 3 commits into
masterfrom
fix/323
Dec 20, 2025
Merged

Fix/323#325
xzel23 merged 3 commits into
masterfrom
fix/323

Conversation

@xzel23

@xzel23 xzel23 commented Dec 20, 2025

Copy link
Copy Markdown
Collaborator

Motivation

The current implementation makes it impossible or at least very cumbersome to configure the jpackage executable correctly when the JDK used for building the project is determined at runtime. The JPackageData would default to the system toolchain instead of the toolchain configured for the jlink task while at the same time, when explicitly setting a value, it is evaluated too early to be bound to a runtime resolved property.

Changes

  • Change javaHome to a DirectoryProperty but add a compatible setter accepting String
  • Turn JPackageData into an Extension
  • Change the JPackage tool resolution to default to jlink.javaHome instead of the system toolchain

All tests pass without changes. Fixes #323 and likely also fixes #214.

@xzel23 xzel23 marked this pull request as ready for review December 20, 2025 05:22
@xzel23 xzel23 merged commit c524483 into master Dec 20, 2025
8 checks passed
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.

jpackage task uses the wrong binary when jpackageHome is not configured but javaHome is Task jpackage Execution failed : 2022

1 participant