Package Details: jabref-git 5.0alpha.r14.g66b7fe3af4-1

Git Clone URL: (read-only)
Package Base: jabref-git
Description: GUI frontend for BibTeX, written in Java -- built from git
Upstream URL:
Licenses: MIT
Conflicts: jabref
Provides: jabref
Submitter: haawda
Maintainer: haawda
Last Packager: haawda
Votes: 13
Popularity: 0.000024
First Submitted: 2012-03-20 17:01
Last Updated: 2019-09-01 12:12

Dependencies (5)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 Next › Last »

haawda commented on 2019-09-15 10:37

Confirmed, see for a discussion.

alleut commented on 2019-09-13 09:49

Jabref does not start: Picked up JAVA_TOOL_OPTIONS: -Xms1g -Xmx1g Error: Could not find or load main class Caused by: java.lang.ClassNotFoundException:

dreieck commented on 2019-02-08 16:32

It downloads stuff (and a big amount of stuff) during build():

==> Starting build()...

This should not happen. During build(), an internet connection cannot be assumed (e.g. someone using makepkg -o, and later makepkg -e).

Best is: makedepend on gradle. If not possible, download it via the sources-array. As an exception, if this is not possible, too, download it in the prepare()-function.

j0hannes commented on 2017-12-01 22:33

JabRef is incompatible with java9:

danmc commented on 2017-11-27 04:08

@j0hannes, I can't seem to reproduce the issue. Are you still having problems with the build? Could you share your version of java?

j0hannes commented on 2017-11-11 19:23

the current version leads to this error message:

Error: Could not find or load main class org.jabref.JabRefMain
Caused by: java.lang.NoClassDefFoundError: javafx/application/Application

danmc commented on 2017-10-12 02:39

The launch script from the original submitter is designed to select the latest version of java by simply sorting the results from a 'find' command, but I don't think that's really recommended by the wiki.

I'm going to set it to use the default determined by archlinux-java. I **think** the issue now will be with users defaulting to jdk7, so I will leave a commented portion in the script for defaulting to jdk8.

salvatoreG commented on 2017-10-09 09:36

It seems like having openjdk-9 breaks the launch script.
/usr/bin/jabref: line 5: /usr/lib/jvm/java-9-openjdk/jre/bin/java: No such file or directory

For openjdk9 the actual path is actually (no /jre/):

I don't think it's because of my setup, here's what is installed:
pacman -Qs openjdk
local/jdk8-openjdk 8.u144-1
OpenJDK Java 8 development kit
local/jdk9-openjdk 9.u181-4
OpenJDK Java 9 development kit
local/jre7-openjdk 7.u151_2.6.11-1
OpenJDK Java 7 full runtime environment
local/jre7-openjdk-headless 7.u151_2.6.11-1
OpenJDK Java 7 headless runtime environment
local/jre8-openjdk 8.u144-1
OpenJDK Java 8 full runtime environment
local/jre8-openjdk-headless 8.u144-1
OpenJDK Java 8 headless runtime environment
local/jre9-openjdk 9.u181-4
OpenJDK Java 9 full runtime environment
local/jre9-openjdk-headless 9.u181-4
OpenJDK Java 9 headless runtime environment

danmc commented on 2017-08-23 23:49

It seems like the maintainers changed their versioning from 4.0.0 to 4.0. I updated the pkgvers() function to just use the annotated git tags as this should prevent this from happening in the future.

bnavarro commented on 2017-08-23 08:42

The update manager always prompt for an update for this package since the version installed doesn't match the advertised version (4.0_v_2.9.2.r7258.d46fd5c84-1 vs 4.0.0_v_2.9.2.r6747.e9a4c7065-1)