Skip to content

jpackage task uses the wrong binary when jpackageHome is not configured but javaHome is #323

@xzel23

Description

@xzel23

When jpackageHome is not configured, the default toolchain java home is used to determine the binary even when javaHome is configured in the extension.

The current resolution is (using pseudo code)):

    JPackageData.jpackageHome ?: defaultToolchainJavaHome(project)

This does not take into account the java home configured in the task itself. Resolution should work like this:

    JPackageData.jpackageHome ?: task.javaHome ?: defaultToolchainJavaHome(project)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions