I'm currently getting the following error on build:
FAILURE: Build failed with an exception.
* Where:
Build file '/home/rhys/.cache/paru/clone/jabref/src/jabref-5.15/build.gradle' line: 14
* What went wrong:
Plugin [id: 'com.github.koppor.gradle-modules-plugin', version: 'jitpack-SNAPSHOT', artifact: 'com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT'] was not found in any of the following sources:
- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Included Builds (No included builds contain this plugin)
- Plugin Repositories (could not resolve plugin artifact 'com.github.koppor:gradle-modules-plugin:jitpack-SNAPSHOT')
Searched in the following repositories:
maven(https://jitpack.io)
Gradle Central Plugin Repository
The -git version seems to work. Maybe upstream needs to make a release?
Pinned Comments
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/jabreflike this?So we can add the
-Djdk.gtk.version=2flag or-Dglass.gtk.uiScale=144dpiflag by cmdline, no need to edit/usr/bin/jabrefafter 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=2flag 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.