Arch Linux User Repository

I have an update for JabRef 4.0 but I have serious issues with this version:
* JabRef does not quit, it stays active after exit waiting for some futex.
* On one machine JabRef needs many minutes to start, checking for duplicate aliases

If you want to try the new package, you can get it from here:
https://github.com/michaellass/AUR/tree/jabref-4/jabref

I will only push it to the AUR as soon as those major issues are solved.

Update: Problem no. 1 is now solved in git, problem no. 2 was a local issue with leftover data from older JabRef versions.

Bevan: Reasonable enough. Thanks for maintaining!

Zebra: Thanks for the feedback! The issue of not properly exiting is now fixed in git by the following three commits:
https://github.com/JabRef/jabref/commit/7ef2b3a01687648d7cdeca1498551426117bdf84
https://github.com/JabRef/jabref/commit/85363d077e42c28ffe7b3cac7cd854c8c8786273
https://github.com/JabRef/jabref/commit/fae290caa38aedbea3a2d093419e5ade4e62d620

I'd like to wait for a release including these fixes before pushing JabRef 4 to AUR.

The other issue of long starting time seemed to be an issue with leftover configuration from an older JabRef version, I could fix it by cleaning that up.

Ogion: Good point, JabRef 4 uses JavaFX now so that package is required. I will add it as a dependency.

The aur Package from your github link works just fine for me, except for one thing: I had to install `java-openjfx` from the repo, before JabRef would actually run. You should probably add that to the Depends.

Bevan: I testet your package just now (4.0.1) and cannot reproduce your issues. Stops at once. start up time is 3.5 seconds max.

I have an update for JabRef 4.0 but I have serious issues with this version:
* JabRef does not quit, it stays active after exit waiting for some futex.
* On one machine JabRef needs many minutes to start, checking for duplicate aliases

If you want to try the new package, you can get it from here:
https://github.com/michaellass/AUR/tree/jabref-4/jabref

I will only push it to the AUR as soon as those major issues are solved.

Update: Problem no. 1 is now solved in git, problem no. 2 was a local issue with leftover data from older JabRef versions.

koppor: Thanks for the updates! The new package release now explicitly calls java 8. I also looked into the .desktop file and the start script. The first has slightly different entries (Icon and StartupWMClass), so we cannot use it as is. But I changed the one provided by this package to be as close as possible. The start script provided here is very specific to Arch Linux as it calls archlinux-java to find out what JVM was selected by the user. So I'm not sure how valuable this is for upstream. It could be a starting point for a more universal start script that supports multiple distributions though.

JabRef will soon release version 4.0, which depends on JavaFX. I think, one has only to add "java-openjfx" to the list of dependencies.

The java-runtime should be set to precisely 8, as JabRef currently does not run at Java9: https://github.com/JabRef/jabref/issues/2594

JabRef now also tries to maintain a .desktop file. See https://github.com/JabRef/jabref/blob/master/buildres/snapcraft/jabref.desktop. Maybe, that file can be used? We can also place it somehwere else in the src tree. Maybe directly at buildres/?

The JabRef team is also often asked to provide a jabref.sh (see https://github.com/JabRef/JabFox/issues/19). Maybe, you could provide your jabref.sh as pull request to JabRef's main repository? I would propose the scripts/ folder as the location.

JabRef has recently had its license updated. The PKGBUILD contains the checksum of the v3.8.2 license, but downloads the license from the master branch (currently v4.x beta), so the checksum test fails.

Try this patch as a fix: http://x7f.uk/jamaxa.patch

@Rhinoceros: Thanks a lot! :)