Package Details: jdtls 0.65.0-1

Git Clone URL: (read-only, click to copy)
Package Base: jdtls
Description: Eclipse Java language server
Upstream URL:
Licenses: EPL
Submitter: languitar
Maintainer: languitar
Last Packager: languitar
Votes: 8
Popularity: 0.191321
First Submitted: 2017-11-15 12:49
Last Updated: 2020-11-20 18:26

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

languitar commented on 2019-05-20 16:57

@GrimKriegor thanks, you're right. Package is updated now.

GrimKriegor commented on 2019-05-19 17:11

Hello there.

It has come to my attention that the latest commit named Version bump to 0.38.0 updates the pkgver variable, but not source nor sha256sums, which still point to the 0.35.0 tar file.

Additionally, version 0.39.0 is already out.

Here is a patch for your consideration:

diff --git a/PKGBUILD b/PKGBUILD
index e9568ff..1d30e25 100644
@@ -1,7 +1,7 @@
 # Maintainer: Johannes Wienke <>

 pkgdesc="Eclipse Java language server"
@@ -9,9 +9,9 @@ url=""

 package() {

Thank you for your time.

languitar commented on 2019-01-19 20:07

I have put a hack in the launcher script to work around the issue. Should work as expected now.

languitar commented on 2019-01-11 19:01

@sum01 strange, on a different computer I am experiencing exactly the same issue, but I am unable to reproduce it on my main machine and I can't spot a difference.

languitar commented on 2019-01-05 17:51

@sum01: I suspect that is a problem of how you call the server. Here, it still works as expected. You can have a look at my vim config for this server:

sum01 commented on 2019-01-05 17:47

The installation does work now, although when trying to run it I get this error <title>Invalid Configuration Location</title>The configuration area at '/usr/share/java/jdtls/config_linux' is not writable. Please choose a writable location using the '-configuration' command line option.

I'm attempting to use it with the LanguageClient-neovim plugin, although that error is from running at command line.

languitar commented on 2019-01-05 10:14

I have updated the package. @sum01, could you test again, please?

languitar commented on 2019-01-05 09:58

Great. The release is just about two weeks old and already an upstream snapshot version is gone again. I will have to change the package to use their released jar files instead to work against these things. Seems, they will continue to use snapshots versions of upstream software for some more time.

sum01 commented on 2019-01-05 01:39

I'm having the same build failure issue with v0.30.0

languitar commented on 2018-10-01 15:00

I have reported this upstream. Let's see what the do about this.