Arch Linux User Repository

@nicolehopperB8Y, @languitar, I have been through that same issue with vim-ale recently.

Hope this helps.

https://github.com/w0rp/ale/pull/2523

@nicolehopperB8Y the only option I see is to somehow replicate what the launcher schript does in vimscript. Or try to get in touch with the coc developer to clarify this.

Btw, I always use the signed releases from the milestone release server and use the sha256 sum provided by upstream.

@languitar I use this package because I don't want coc to manage it. When updating I can check the pkgbuild if I use aur, but when coc updates I don't know which file it's downloading...

@nicolehopperB8Y ships it's own copy of jdtls, which should be installed somewhere into your home directory. I don't see why you shouldn't be able to write there. Try to check the permissions. You don't event need this package for coc.

@languitar is there any other way to work around the issue? I'm using coc.nvim & coc-java, but coc-java just run the jdtls server directly so the launcher script is useless to me.

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

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
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Johannes Wienke <languitar@semipol.de>

 pkgname=jdtls
-pkgver=0.38.0
+pkgver=0.39.0
 pkgrel=1
 pkgdesc="Eclipse Java language server"
 arch=(any)
@@ -9,9 +9,9 @@ url="https://github.com/eclipse/eclipse.jdt.ls"
 license=('EPL')
 depends=('java-runtime')
 makedepends=()
-source=("http://download.eclipse.org/jdtls/milestones/0.35.0/jdt-language-server-0.35.0-201903142358.tar.gz"
+source=("http://download.eclipse.org/jdtls/milestones/0.39.0/jdt-language-server-0.39.0-201905150127.tar.gz"
         "launcher.sh")
-sha256sums=('f51f804e5c6d1a1674d78433f1530faeba46b86da86a8bae2ed55690d2c28204'
+sha256sums=('2bc0e44c337ea1fb68df6bcb29267f112ec6dddc4e28114a99e35332966153c1'
             '813801c237676764f6fb005df3ccaaee33c7cc0ab54fc1c73ef3cf4cee5a65de')

 package() {

Thank you for your time.

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

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

@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: https://github.com/languitar/config-vim/blob/master/home/.config/nvim/init.vim#L365