Package Details: jabref 5.13-1

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: 212
Popularity: 2.89
First Submitted: 2012-06-07 22:47 (UTC)
Last Updated: 2024-04-02 16:01 (UTC)

Dependencies (4)

Required by (0)

Sources (6)

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?

............
--module-path ${ROOT}/lib \
${JABREF_EXT_Options} \
--patch-module .............

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.

JABREF_EXT_Options='-Dglass.gtk.uiScale=144dpi -Djdk.gtk.version=2' jabref

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 21 Next › Last »

vanja_z commented on 2023-09-24 10:55 (UTC)

Task :compileJava FAILED

FAILURE: Build failed with an exception.

  • What went wrong: 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.

swsnr commented on 2023-09-02 08:34 (UTC)

Nice, thanks for the quick update!

Bevan commented on 2023-09-02 08:30 (UTC)

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.

swsnr commented on 2023-09-02 05:13 (UTC)

5.10 seems to require OpenJDK 21 which is not yet released.

faebu commented on 2023-01-02 06:41 (UTC)

Hi Bevan, thanks for the prompt reply, after renaming /home/<user>/.m2/repository the build went through without problems👍 Thanks for your work!

Bevan commented on 2023-01-01 20:28 (UTC)

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...

faebu commented on 2023-01-01 20:04 (UTC) (edited on 2023-01-01 20:07 (UTC) by faebu)

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!

Bevan commented on 2022-12-05 20:17 (UTC)

@daniel_shub: Thanks for the report. This is something that needs a bit of thinking and testing. Not sure if this is an issue in archlinux-java-run or in this and probably other packages using it. For now, I transformed it into a github issue, so I don't forget: https://github.com/michaellass/AUR/issues/34

daniel_shub commented on 2022-12-02 17:40 (UTC)

I am having trouble building in a clean chroot with makechrootpkg.

==> Starting build()... Your Java installation is not set up correctly. Try archlinux-java fix. Using JDK from to build JabRef.

ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

Please set the JAVA_HOME variable in your environment to match the location of your Java installation.

==> ERROR: A failure occurred in build(). Aborting...

I am installing jdk18-openj9-bin and archlinux-java-run from the AUR.

resolving dependencies... looking for conflicting packages...

Packages (6) java-environment-common-3-3 java-runtime-common-3-3 nspr-4.35-1 nss-3.85-1 archlinux-java-run-9-1 jdk18-openj9-bin-18.0.2.1-1

I think the recommendation to run "archlinux-java fix" is correct since if I manually enter the chroot and then run the "archlinux-java-run" command from the PKGBUILD, it does not return anything but if I run "archlinux-java fix", then the PKGBUILD command gives the correct version.

The issue, I think is that I cannot simply add "archlinux-java fix" to the build function in the PKGBUILD since the archlinux-java script requires root privileges and makechrootpkg drops privileges (I think).

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 21 Next › Last »