Merged
Conversation
- add opinionated init options to replace the old example - initialization_options are now a child of lsp.jdtls - add a per project init option resolving a common issue with non Gradle or Maven projects
playdohface
approved these changes
Mar 1, 2026
Collaborator
playdohface
left a comment
playdohface
left a comment
There was a problem hiding this comment.
Nice, how did you arrive at the specific init options?
Collaborator
Author
|
These are the options I run daily. I've been spamming these for the past few months under the issues when some import or signature was causing problems. They are mostly based on the previous example plus some addition here and there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.