Skip to content

Update JavaSE-17 references to JavaSE-21 for JDTLS JRE upgrade - #138

Closed
Lakshya A Agrawal (LakshyAAAgrawal) wants to merge 1 commit into
microsoft:mainfrom
LakshyAAAgrawal:fix/jdtls-javase-21-references
Closed

Lakshya A Agrawal (LakshyAAAgrawal) wants to merge 1 commit into
microsoft:mainfrom
LakshyAAAgrawal:fix/jdtls-javase-21-references

Conversation

@LakshyAAAgrawal

Copy link
Copy Markdown
Collaborator

Summary

The JRE bundled with vscode-java was upgraded from Java 17 to Java 21 in #126, but the JavaSE runtime name references were not updated. Without this fix, JDTLS initialization fails with an assertion error because the assert expects JavaSE-17 in the config but the JSON now specifies Java 21 paths.

Changes

  • eclipse_jdtls.py: JavaSE-17 → JavaSE-21 in runtime config assert and assignment (2 lines)
  • initialize_params.json: JavaSE-17 → JavaSE-21 (1 line)

Attribution

This issue was caught by Stephen Rayner (@gruckion) in #128. The commit is authored by them.

Merge after #126.

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

Copy link
Copy Markdown
Collaborator Author

Superseded by #139 which includes the full JDTLS upgrade with the JavaSE-21 fix.

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