Package Details: jabref 5.0-3

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: 197
Popularity: 3.11
First Submitted: 2012-06-07 22:47
Last Updated: 2020-03-29 16:22

Dependencies (3)

Required by (0)

Sources (3)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

quickwater commented on 2020-05-05 19:11

Bevan: I have tried getting the files manually by wget or using a browser. Sometimes it worked, sometimes it gave me 404. However, your idea about firewall made me think that it could be a problem with a Brazilian internet provider. I connected to a VPN, et voilà, everything is working fine. So everything seems to be resolved. Thanks a lot for your help.

Bevan commented on 2020-05-05 18:49

quickwater: Thanks for clarifying. Since the problem is not specific to this package, it's unlikely that we can solve it here. But maybe we can learn something about the issue nevertheless.

In your first post you mentioned https://jcenter.bintray.com/org/openjdk/jmh/jmh-core/1.21/jmh-core-1.21.jar as not downloadable. What happens if you manually try to download that file, e.g., using

curl --output jmh-core-1.21.jar -L https://jcenter.bintray.com/org/openjdk/jmh/jmh-core/1.21/jmh-core-1.21.jar

or

wget https://jcenter.bintray.com/org/openjdk/jmh/jmh-core/1.21/jmh-core-1.21.jar

? Are you maybe behind some kind of firewall? Either because you are using a company network or maybe you are in a state that filters internet access?

quickwater commented on 2020-05-05 18:33

Bevan: no, it wasn't resolved. I deleted the comment because I wanted to try to solve it first, before asking help here. Looks like it is not temporary problem. I am sure it is not in PKGBUILD, since I tried to build jabref from the git repository with the same result.

Bevan commented on 2020-05-05 16:13

quickwater: Wasn't this issue solved five days ago (since you deleted your first comment on that)? I tried building when you posted this first and it worked for me so I assumed it was a temporary hickup.

quickwater commented on 2020-05-05 16:01

Cannot build because gradle cannot get resources such as jmh-core, xstream, javaparser-symbol-solver-core-3.13.5.jar and others. What could be a possible reason? Thanks.

Bevan commented on 2020-04-03 09:22

neXyon: It is already adependency: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jabref#n16

neXyon commented on 2020-04-03 09:20

Please add archlinux-java-run as dependency!

sirocco commented on 2020-04-01 08:17

Performance issues with version 5.0 (large databases)

https://github.com/JabRef/jabref/issues/5071

Bevan commented on 2020-03-31 14:37

hseara: I also observed the issue of JabRef not properly closing a couple times, however I could never reproduce it reliably. Also startup times are quite high. Overall it is usable for me but I only deal with relatively small bib files and typically have only one open at a time.

I do think these are upstream issues but we should indeed make sure before you report the issues upstream. To do so, you can download the "JabRef Linux Portable" version from https://www.fosshub.com/JabRef.html

You can then launch it as follows:

tar xf JabRef-5.0-portable_linux.tar.gz
cd JabRef
bin/JabRef

hseara commented on 2020-03-31 14:29

Hi all, after the update to JabRef 5, the program is slow. In my case with 20 local bib files opened with a maximum of 1000 entries in some of them, it is hardly usable. Opening the program to an entirely usable state takes close to a minute. Changing from a tab (i.e. bib file) to another tab (i.e., bib file) takes 10 or more seconds. Closing the program also takes a long time. Moreover, after closing the program, java is often not always closed properly using resources in the background until manually killed. Is anybody else experiencing all these issues? If so, is this a problem of the archlinux installation, or should we start reporting all this upstream? I did not want to pollute upstream with issues if they are just arch centric and solvable by us.