Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove unnecessary jdt.ls config #121

Merged
merged 1 commit into from
Sep 26, 2021
Merged

Conversation

fbricon
Copy link
Contributor

@fbricon fbricon commented Sep 26, 2021

jdt.ls project lead here. I noticed the jdt.ls config referenced missing bundles or unsupported configuration, so I just removed them.

@raxod502
Copy link
Member

Thanks! I ran this locally and autocompletion still looks great, so, merging this!

image

While I've got you here, though, I was wondering, what would you recommend as the bare minimum way to set up a "project" that jdt.ls would be happy with, to clear the warning above? In Riju's environment, you only ever have one source file, but I assume Riju needs to automatically create a file in the directory to configure a "project" as well?

@raxod502 raxod502 merged commit 1646f89 into radian-software:master Sep 26, 2021
@raxod502 raxod502 mentioned this pull request Sep 26, 2021
@maxandersen
Copy link

@raxod502 if you enabled jbang here it would generate the project info for you - just saying :)

@fbricon
Copy link
Contributor Author

fbricon commented Sep 29, 2021

@raxod502 you need the source directory and the jdt.ls workspace (-data) to be different, the workspace shouldn't be nested under the sources, and vice-versa, and send a triggerFile parameter
So, if your source lives in $PWD, basically start the server with -data=/someting/different/jdt/specific.

then add :

  • rootUri: file://$PWD
  • triggerFiles:
    • file://$PWD/Main.java

raxod502 added a commit that referenced this pull request Oct 3, 2021
@raxod502
Copy link
Member

raxod502 commented Oct 3, 2021

Thank you! I changed the data directory in efaaf73 and it appears to be working great (at least locally)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants