Version 1.35.0 does not perform Suggestions, Corrections, or Highlighting

[Obscure2020]

I noticed that this extension had stopped starting up right when I noticed that it didn't update the code highlighting and coloring on startup anymore. Version 1.35.0 of this extension does not perform any of the following:

• Applying correct Java-specific coloring to the text upon startup
• Applying red underlining to malformed function calls
• Applying blue underlining to TODO comments
• Highlighting all occurrences of the word underneath the cursor

There are probably even more missing features, but these are the ones I noticed. Under version 1.35.0, one of my simple code files looks like this:

Reverting to version 1.34.0 of the extension and then restarting my extensions immediately restores all lost functionality:

Environment:

• Operating System: Windows 11 Home, 23H2
• JDK version: openjdk 22.0.2 2024-07-16
• Visual Studio Code version: 1.93.1

[snjeza]

@Obscure2020 Do you have a project example reproducing the issue?

[testforstephen]

@snjeza please try more projects. On Windows, I can reproduce it in some projects, some are not. Don't find the pattern yet.

[testforstephen]

I can always reproduce it with spring-petclinic project. When I use the command Help: Start Extension Bisect to detect the potential extension that causes the problem, it tells that Spring Boot Tools extension (v1.58.2024092800) causes this problem. And disable it, the word highlighting will come back. Downgrading vscode-java to 1.34 won't fix the issue.

Add @martinlippert for more insights on this issue.

[Obscure2020]

@snjeza The project I was working on contained only two .java files and one .txt file. I have zipped these files together, and you can download the .zip here: SampleProj.zip

[snjeza]

@Obscure2020 Could you try to disable the Spring Boot extension?

[Obscure2020]

I believe the Spring Boot extension is a red herring. I do not have the Spring Boot extension installed, nor have I ever had the Spring Boot extension installed. The Spring Boot extension is certainly not a contributing factor in the bad behavior of version 1.35.0 on my system.

Here are all of the extensions I have installed at this time, which have remained unchanged as I switch between version 1.34.0 and version 1.35.0:

[Obscure2020]

I can also confirm that version 1.35.1 is just as broken as 1.35.0. None of the features that 1.35.0 broke are fixed by 1.35.1, at least on my system. 1.34.0 remains the most recent version that works properly.

[nikunjk9]

@Obscure2020 Is the extension compatible with your current editor version?

I have faced the same issue, sometimes, newer versions of extensions may have compatibility issues with older versions of an editor. Ensure that both the extension and the editor are up to date.

[Obscure2020]

@nikunjk9 I said in my original post, at the bottom, that I am using version 1.93.1 of VSCode. As far as I'm aware, this is the latest version. Clicking the Check for Updates... button just brings up a popup that says "There are currently no updates available."

Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

[Obscure2020]

Versions 1.35.1 and 1.35.0 are still broken on version 1.94.0 of VSCode. Version 1.34.0 of this plugin remains the most recent version that actually functions.

Version: 1.94.0 (user setup)
Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
Date: 2024-10-02T13:08:12.626Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631