| Git Clone URL: | https://aur.archlinux.org/jabref.git (read-only, click to copy) |
|---|---|
| Package Base: | jabref |
| Description: | Graphical Java application for managing BibTeX and biblatex (.bib) databases |
| Upstream URL: | https://www.jabref.org/ |
| Licenses: | MIT |
| Submitter: | Allan |
| Maintainer: | Bevan |
| Last Packager: | Bevan |
| Votes: | 215 |
| Popularity: | 0.97 |
| First Submitted: | 2012-06-07 22:47 (UTC) |
| Last Updated: | 2025-01-17 16:00 (UTC) |
@carlosal1015: I tried with Java 17 and while building the package works, launching JabRef does not. So I think at least version 20 is required.
@Pavlov and @vanja_z: I could not reproduce your issue yet. Can you please post the output of the following commands?
Hi, is mandatory java-runtime>=20 or could be relaxed until 17?
Even with archlinux-java-run=10-1 the problem persists:
Execution failed for task ':compileJava'.
> Error while evaluating property 'javaCompiler' of task ':compileJava'.
> Failed to calculate the value of task ':compileJava' property 'javaCompiler'.
> No matching toolchains found for requested specification: {languageVersion=20, vendor=any, implementation=vendor-specific} for LINUX on x86_64.
> No locally installed toolchains match and toolchain download repositories have not been configured.
Sorry, I missed to update archlinux-java-run in time for JDK 21 which caused issues with building or running Java applications that use it. Please update archlinux-java-run to v10 and report back if there are still any issues afterwards.
Task :compileJava FAILED
FAILURE: Build failed with an exception.
Error while evaluating property 'javaCompiler' of task ':compileJava'. Failed to calculate the value of task ':compileJava' property 'javaCompiler'. > No matching toolchains found for requested specification: {languageVersion=20, vendor=any, implementation=vendor-specific} for LINUX on x86_64. > No locally installed toolchains match and toolchain download repositories have not been configured.
Nice, thanks for the quick update!
Luckily, that JDK 21 requirement is only due to a bug in jlink, which we do not use when building JabRef. So, updating to 5.10 is possible with JDK 20.
5.10 seems to require OpenJDK 21 which is not yet released.
Hi Bevan, thanks for the prompt reply, after renaming /home/<user>/.m2/repository the build went through without problems👍 Thanks for your work!
faebu: I cannot reproduce that problem. However, from the output it looks like gradle is only searching for the jar files within your maven cache (/home/<user>/.m2/repository) and not in the online repositories. You truncated the output, so maybe it's checking other locations later on.
The first thing I would try is to remove that cache, i.e., delete the folder /home/<user>/.m2/repository or temporarily rename it if you want to keep it.
What's a bit annoying is that all those jar files that are missing are deleted later anyway. But I don't know if/how it is possible to make gradle skip these files already during build...
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/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.