JPackage working directory in subproject incorrect with Gradle 8.12

[bjorndarri]

I ran into this problem today, the jpackage command could not locate icons with relative paths.

Looks like something changed between Gradle 8.11.1 and 8.12, which is causing the jpackage command to be run with the root project directory as working directory, instead of the subroject directory (this may be affecting other tasks as well, I haven't checked).

The project structure:

chinook root project

chinook/chinook-client-local subproject

Command:

gradle chinook-client-local:jpackage

Here's the the log output, indicating the problem in Working directory:

Gradle 8.11.1, correct working directory:

2025-01-02T15:59:11.146+0000 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command '/home/user/jdk/linux/jdk-23/bin/jpackage''. Working directory: /home/user/Projects/github/chinook/chinook-client-local Command: /home/user/jdk/linux/jdk-23/bin/jpackage [rest truncated]

Gradle 8.12, working directory is now the root project directory:

2025-01-02T16:00:40.290+0000 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command '/home/user/jdk/linux/jdk-23/bin/jpackage''. Working directory: /home/user/Projects/github/chinook Command: /home/user/jdk/linux/jdk-23/bin/jpackage [rest truncated]

I did a rather quick'n dirty test to see if the problem was in Gradle, by creating a simple JavaExec task in a subproject, with a main class which just printed out user.dir, and that output looked correct.

I also skimmed over the 8.12 release notes and didn't see anything which looked relevant.

I'm afraid I don't really have the know-how to figure this one out, but I'll play with this if I have time in the next few days, and report back if I find anything out.

[bjorndarri]

Reproducer

https://github.com/bjorndarri/jlink-288-reproducer

[xzel23]

I can reproduce the problem. Will look into this later.

[armin-reichert]

Same issue here, seems to be this Gradle regression bug: gradle/gradle#31942

[xzel23]

@armin-reichert Thank you for this information. As this seems indeed to be a Gradle bug, I will wait for the Gradle fix. If unexpectedly the problem is not solved when Gradle releases their fix, I will look into this again.

In the meantime, please downgrade Gradle to 8.11.1.