Skip to content

Update runtime dependencies for Java Language Server - #126

Closed
Tim Vergenz (vergenzt) wants to merge 3 commits into
microsoft:mainfrom
vergenzt:patch-1
Closed

Tim Vergenz (vergenzt) wants to merge 3 commits into
microsoft:mainfrom
vergenzt:patch-1

Conversation

@vergenzt

Copy link
Copy Markdown

No description provided.

@vergenzt

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@LakshyAAAgrawal

Copy link
Copy Markdown
Collaborator

This looks good! One issue: the JRE paths are upgraded to Java 21, but initialize_params.json and eclipse_jdtls.py still reference JavaSE-17. This would cause an assertion failure at runtime.

I'll push a follow-up commit after merging to fix this. Credit to Stephen Rayner (@gruckion) who caught this in #128.

Lakshya A Agrawal (LakshyAAAgrawal) pushed a commit to LakshyAAAgrawal/multilspy-cicd-fix that referenced this pull request Apr 10, 2026
The JRE bundled with vscode-java was upgraded from Java 17 to Java 21
in microsoft#126, but the JavaSE runtime name references in eclipse_jdtls.py
and initialize_params.json were not updated. This causes an assertion
failure at runtime because the assert expects JavaSE-17 in the config
but the JSON now specifies Java 21 paths.

Caught by @gruckion in microsoft#128.
Lakshya A Agrawal (LakshyAAAgrawal) pushed a commit to LakshyAAAgrawal/multilspy-cicd-fix that referenced this pull request Apr 10, 2026
Upgrade Eclipse JDTLS runtime dependencies:
- vscode-java: v1.23.0 -> v1.46.0
- Bundled JRE: Java 17 -> Java 21 (JavaSE-17 -> JavaSE-21)
- Gradle: 7.3.3 -> 7.6.6 (with templated URL)
- Lombok: 1.18.30 -> 1.18.39
- IntelliCode: 1.2.30 -> 1.3.2
- Equinox launcher: 1.6.500 -> 1.7.0
- Fix osx-arm64: was incorrectly downloading x64 binary

Based on work by @vergenzt (microsoft#126) and @gruckion (microsoft#128).
Closes microsoft#126, closes microsoft#128.

Contributed-by: Tim Vergenz <vergenzt@users.noreply.github.com>
Contributed-by: Stephen Rayner <contact@gruckion.com>
@LakshyAAAgrawal

Copy link
Copy Markdown
Collaborator

Thank you Tim Vergenz (@vergenzt)! Your changes are incorporated into #139 which resolves the merge conflicts with current main. You're credited as a contributor in the commit message.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants