-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JPackageImageTask property 'imageDir' specifies directory '/project/build/image' which doesn't exist #243
Comments
I've created a fork https://github.com/bjorndarri/badass-jlink-plugin with my fix, I'd appreciate it if someone would check if the problem described in #237 has been re-introduced by this change. |
FYI, I tried testing this by cloning https://github.com/JabRef/jabref and running |
I would appreciate it if you could test this, since all my I've been considering the problem, and have a feeling #237 is based on a misunderstanding. These are the default dependencies between these tasks, as far as I can tell:
Making |
Which JDK do you have? 21u1 works. All before don't. Reason: We fixed the linked issue, but it takes time until the fix is present in a JDK release. I can't currently check the availability of JDK 21u1. Our custom build https://files.jabref.org/jdks/ works. |
I managed to build JabRef successfully with the recently released JDK 21.0.1. But I'm afraid the #237 problem remains, when the I'm pretty sure that the changes made in #237 were not the right thing to do, when the So, what to do? I'm of the opinion that the changes made in #237 should be reverted and version 3.0.1 released, and that the JabRef build should simply keep using What do you guys think? @koppor @airsquared |
Is it possible to provide more details here?
This is fine with me. - However, I think, "proper" input and output dependencies would be great. Nevertheless, if I am the only one having issues (with an easy workaround), reverting is really fine! |
For details, see this issue, first comment. |
Try this patch:
|
Thank you very much @airsquared, this patch fixed my problem (this issue, just to be clear)! |
I pushed the change to master; @koppor could you verify that this change doesn't break anything for you? |
@airsquared I do not get any build errors. Tested at koppor/jabref#660 - jlinkZip.dependsOn jpackage The binaries run well - thus, a Installation:
|
Great, thanks for testing! |
I just tested with the current master and everything is working correctly. |
Closing this, thanks guys! |
Hey there,
I'm running into a problem with version 3.0.0 of this plugin, when I run the
jpackage
task I get the following output:A problem was found with the configuration of task ':jpackageImage' (type 'JPackageImageTask'). In plugin 'org.beryx.jlink' type 'org.beryx.jlink.JPackageImageTask' property 'imageDir' specifies directory '/home/darri/minimal/build/image' which doesn't exist.
This problem is related to this line, where I set the
imageName
property in the jlink task:the problem disappears when I remove that line.
I've created a minimal project reproducing the error:
https://github.com/bjorndarri/jpackage-error
Just run the `jpackage' task.
I've traced the problem to the following commit (#237): 98a5ad1
I tried changing
getImageDir()
from@OutputDirectory
back to@InputDirectory
in bothJPackageImageTask
andJPackageTask
, like it was before the above commit, while not touchinggetImageOutputDir()
, and that solved the problem.Regarding #237, I've been using the jpackage and jlinkZip tasks extensively for the last couple of years, and have never run into the problem described there. Could it be that this is a result of some misconfiguration, as opposed to a plugin bug?
Now, I'm no Gradle plugin expert and don't really know what I'm doing here, so we're going to have to figure this out somehow 😃.
ps. @airsquared thanks for picking up the torch and assisting with this plugin, it's an absolute life saver.
The text was updated successfully, but these errors were encountered: