Hi, I am on Manjaro and get the following error when building jabref:
...
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':startScripts'.
> Error while evaluating property 'relativeClasspath' of task ':startScripts'
> Could not resolve all files for configuration ':runtimeClasspath'.
> Could not find javafx-fxml-19-win.jar (org.openjfx:javafx-fxml:19).
Searched in the following locations:
file:/home/<user>/.m2/repository/org/openjfx/javafx-fxml/19/javafx-fxml-19-win.jar
> Could not find javafx-controls-19-win.jar (org.openjfx:javafx-controls:19).
Searched in the following locations:
file:/home/<user>/.m2/repository/org/openjfx/javafx-controls/19/javafx-controls-19-win.jar
> Could not find javafx-graphics-19-win.jar (org.openjfx:javafx-graphics:19).
Searched in the following locations:
file:/home/<user>/.m2/repository/org/openjfx/javafx-graphics/19/javafx-graphics-19-win.jar
> Could not find javafx-base-19-win.jar (org.openjfx:javafx-base:19).
Searched in the following locations:
file:/home/<user>/.m2/repository/org/openjfx/javafx-base/19/javafx-base-19-win.jar
...
I have installed the following Java/JDK packages (all up to date):
archlinux-java-run 9-1 AUR 16.8 kB
java-environment-common 3-3 extra
java-hamcrest 1.3-5 extra 312.5 kB
java-openjfx 19.u11-1 extra 152.9 MB
java-runtime-common 3-3 extra 5.4 kB
jdk-openjdk 19.0.1.u10-3 extra 97.6 MB
jdk17-openjdk 17.0.5.u1-1 extra 92.7 MB
jre-openjdk 19.0.1.u10-3 extra 515.5 kB
jre-openjdk-headless 19.0.1.u10-3 extra 186.7 MB
jre17-openjdk 17.0.5.u1-1 extra 515.5 kB
jre17-openjdk-headless 17.0.5.u1-1 extra 176.0 MB
Any idea how to resolve the error, do I need to fix something in the build files or install some additional package?
Thanks and happy new year!
Pinned Comments
Bevan commented on 2024-03-28 17:57 (UTC)
Everyone who struggles to update right now: Please install the jdk21-openjdk package. It provides java-environment=21.
Bevan commented on 2022-03-14 20:04 (UTC)
@shmilee: I like that idea. Implemented in 5.5-2 using JABREF_OPTIONS as variable name.
Note that you can then also put that environment variable into your .bashrc, .pam_environment or something similar to be automatically applied.
shmilee commented on 2022-03-12 13:51 (UTC)
How about add an extra JavaOptions variable in launch script
/usr/bin/jabref
like this?So we can add the
-Djdk.gtk.version=2
flag or-Dglass.gtk.uiScale=144dpi
flag by cmdline, no need to edit/usr/bin/jabref
after upgrade.matteodelabre commented on 2020-11-17 14:25 (UTC)
Using JabRef with i3wm, I’m running into the issue described at https://github.com/JabRef/jabref/issues/5867 in which clicking the menu bar sometimes opens then immediately closes the associated menu, rendering it unusable.
I was able to fix this issue by adding the
-Djdk.gtk.version=2
flag after line 9 in https://aur.archlinux.org/cgit/aur.git/tree/jabref.sh?h=jabref (as suggested in the related bug report https://bugs.openjdk.java.net/browse/JDK-8251240). This change also removes the “XSetErrorHandler() called with a GDK error trap pushed. Don't do that.” warning mentioned by ruiin in a previous comment.So far, I have not encountered any adverse side-effect from this workaround.