@Flupp: The tar is created during build, so it's not coming from upstream directly. Weirdly, I cannot reproduce your problem:
tar tvf src/jabref-5.6/build/distributions/JabRef-5.6.tar | grep codec
-rw-r--r-- 0/0 335042 2020-03-29 19:14 JabRef-5.6/lib/commons-codec-1.11.jar
And similarly, it's correct in pkg as well:
ls -la pkg/jabref/usr/share/java/jabref/lib/commons-codec-1.11.jar
-rw-r--r-- 1 bevan bevan 335042 6. Mai 20:25 pkg/jabref/usr/share/java/jabref/lib/commons-codec-1.11.jar
I wonder if this depends on the Java version used during the build step. Maybe gradle fetches different sources then. When running makepkg, there will be an output like the following:
Using JDK from /usr/lib/jvm/java-18-openjdk to build JabRef.
What does it say in your case?
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.