You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An issue has been opened in the LSP4Jakarta repo to remove the usage of the internal JDT class: eclipse-lsp4jakarta/lsp4jakarta#517. In the meantime, users can apply the following workaround to re-enable Jakarta diagnostics:
Install v1.26.0 of Language Support for Java(TM) by Red Hat
Since the latest versions of the Tools for MicroProfile extension are not compatible with v1.26.0 of Language Support for Java(TM) by Red Hat, users will also need to install the pre-release version v0.11.2024012703 of Tools for MicroProfile to have the latest version available that is compatible with v1.26.0 of Language Support for Java(TM) by Red Hat.
Steps to install another version of an extension:
Navigate to the Extensions tab
Find the extension to update under the Installed section
Select the gear icon
Select Install Another Version... (for Tools for MicroProfile, select Switch to Pre-release Version first)
Select the version you would like to install
The text was updated successfully, but these errors were encountered:
TrevCraw
changed the title
Jakarta diagnostics no longer appearing for v23.0.12 in latest VS Code version (1.86.x)
Jakarta diagnostics no longer appearing for Liberty Tools v23.0.12 in latest VS Code version (1.86.x)
Feb 12, 2024
When VS Code is updated to 1.86.x, dependency extensions for LT VS Code are also updated. When the Language Support for Java extension is updated to v1.27.0, it breaks the diagnostic support from LSP4Jakarta. This is due to LSP4Jakarta using an internal class from the JDT...
https://github.com/eclipse/lsp4jakarta/blob/main/jakarta.jdt/org.eclipse.lsp4jakarta.jdt.core/src/main/java/org/eclipse/lsp4jakarta/jdt/internal/DiagnosticUtils.java#L121-L125
...which was modified in the latest JDT release
eclipse-jdt/eclipse.jdt.core@4556ac2#diff-c8cd805ea463f0b6ca1b6b31a5769d1a25eff919b513631fb3dd48c1d7c962c7
Workaround
An issue has been opened in the LSP4Jakarta repo to remove the usage of the internal JDT class: eclipse-lsp4jakarta/lsp4jakarta#517. In the meantime, users can apply the following workaround to re-enable Jakarta diagnostics:
Steps to install another version of an extension:
The text was updated successfully, but these errors were encountered: