Package Details: jdtls 1.35.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-2.0
Submitter: languitar
Maintainer: languitar
Last Packager: languitar
Votes: 28
Popularity: 0.192899
First Submitted: 2017-11-15 12:49 (UTC)
Last Updated: 2024-04-25 21:33 (UTC)

Dependencies (2)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4

languitar commented on 2019-01-05 17:51 (UTC) (edited on 2019-01-05 17:51 (UTC) by languitar)

@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

sum01 commented on 2019-01-05 17:47 (UTC)

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 (UTC)

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

languitar commented on 2019-01-05 09:58 (UTC)

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 (UTC)

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

languitar commented on 2018-10-01 15:00 (UTC)

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

https://github.com/eclipse/eclipse.jdt.ls/issues/810

<deleted-account> commented on 2018-10-01 14:22 (UTC)

@languitar Yeah, it's repeatable, does look like an upstream issue.

However, I was able to build jdtls using YouCompleteMe (following these instructions: https://www.reddit.com/r/vim/comments/844bwy/has_anyone_gotten_java_language_server_to_work/e2o5hhr). Somehow it manages to overcome the issue, interesting to look at the magic it does to build it.

languitar commented on 2018-10-01 07:05 (UTC)

@zoresvit is this repeatable? if so, this is an upstream issue, because some of the configured maven repositories seem to be gone.

<deleted-account> commented on 2018-09-30 20:10 (UTC)

The build fails with the following error:

[ERROR] Failed to resolve target definition /tmp/yaytmp-1000/jdtls/src/eclipse.jdt.ls-0.25.0/org.eclipse.jdt.ls.target/org.eclipse.jdt.ls.tp.target: Failed to load p2 metadata repository from location http://download.eclipse.org/eclipse/updates/4.9-I-builds/: No repository found at http://download.eclipse.org/eclipse/updates/4.9-I-builds. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
==> ERROR: A failure occurred in build().
    Aborting...
Error making: jdtls

« First ‹ Previous 1 2 3 4