Package Details: jdtls 0.65.0-1

Git Clone URL: https://aur.archlinux.org/jdtls.git (read-only, click to copy)
Package Base: jdtls
Description: Eclipse Java language server
Upstream URL: https://github.com/eclipse/eclipse.jdt.ls
Licenses: EPL
Submitter: languitar
Maintainer: languitar
Last Packager: languitar
Votes: 8
Popularity: 0.181978
First Submitted: 2017-11-15 12:49
Last Updated: 2020-11-20 18:26

Latest Comments

1 2 3 Next › Last »

languitar commented on 2020-11-20 18:13

@cwtb I started packaging this by using the git repository. Sometimes this failed, so I got in contact with the jdtls developers and they indicated that the preferred way of distributing jdtls is to use the milestone builds. I don't understand why the snapshot version is so much ahead of the milestone builds. May be this is something to be asked upstream.

cwtb commented on 2020-11-20 15:23

Have you looked into using snapshots instead of milestone releases keeping things updated? It looks like there is a version here that isn't in the milestones yet. Might not be as stable, but who knows https://download.eclipse.org/jdtls/snapshots/

brainplot commented on 2020-02-19 07:59

@languitar You can expand the ${pkgver} variable in the url so that you don't have to change it in multiple places, whenever there's an update.

languitar commented on 2020-02-07 08:12

I'd love to update this package, but upstream - again - hasn't released a milestone build for the new version. I have, again, pinged them in a Github issue: https://github.com/eclipse/eclipse.jdt.ls/issues/1208

languitar commented on 2019-10-12 13:46

Version bump to 0.44.0 is currently impossible because upstream has not published an artifact using the normal channel: https://github.com/eclipse/eclipse.jdt.ls/issues/1208

GrimKriegor commented on 2019-05-28 19:55

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

Hope this helps.

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

languitar commented on 2019-05-28 19:45

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

nicolehopperB8Y commented on 2019-05-27 05:59

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

languitar commented on 2019-05-26 12:34

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

nicolehopperB8Y commented on 2019-05-25 11:02

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