-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java Extension no longer highlights all occurrences of the word under the cursor in Java files #3787
Comments
I can't reproduce the issue on Linux or Windows. |
I can reproduce the issue on Windows. Tell me, does this issue go away if you revert to version 1.34.0 of the extension? (In the extensions menu, click the gear icon on the extension and select |
Hi @Obscure2020 , @snjeza , I will try with version 1.34.0. and update. Meanwhile, I just updated to version 1.35.1 of the extension and the issue persists. Also, when I double-click the element the "yellow" marks on the minimap, showing all occurrences, no longer available as well. Thanks |
Hi @Obscure2020 , @snjeza , I tested with 1.34.0 and 1.32.0 and the issue is the same. However, I noticed something interesting that can hint to the root cause. Steps:
Thanks |
I had same problem. Disabling all Spring Boot extensions solved the issue. |
Hi, Any update on the issue? The current behavior noticeably reduces the work experience with Java projects, especially long and legacy ones. Thanks |
Can confirm that it seems the Spring Boot extensions are conflicting somehow, as @simogab98 said disabling these allows it to work again |
Yes, verified the same as well, however, disabling Spring Boot extension is not the solution. It shows possible root cause but requires to be taken forward to understand where is a clash between two extensions. Both of them are needed for efficient and productive work on Java Spring (Boot)-based projects. Vitaly |
@vitalyla you can try to add
to your settings.json and restart VS Code |
I tried changing that setting, but it had no effect on the issue. |
@Obscure2020 I tried:
All versions presented the same problem. |
I'm also using MacOS, Sonoma 14.6.1. It seems like the only thing that works as a workaround is freezing Spring Boot Dashboard to version v0.13.1. |
@martinlippert does that ring a bell? |
I think my test was not accurate, sorry for that. As @vitalyla pointed, highlight seems to work for a few seconds after restart VSCode. I realize downgrade doesn't seem to really solve the problem.
I was also using VSCode 1.93.1, exactly the same as @vitalyla, but I tried a newer version (1.94.1) with no success. For now, it seems the only way to work is disabling Spring Boot Tools. |
This seems to be a similar issue: #3789 |
I can reproduce this with the (there might be some confusion coming up because the dashboard extension depends on the I filed spring-projects/sts4#1380 to track work on this in the Spring Tools extension. Sorry for causing this issue. |
I pushed a fix for this to the Spring Tools, now waiting for CI builds to ship this to you as a pre-release... Stay tuned... |
The latest pre-release of the Spring Boot Tools extension got published if you want to give it a try. Switch to the latest pre-release from within your VSCode installation works by looking up the Spring Boot Tools in the list of installed extensions and then "Switch to Pre-Release Version". |
Hi @martinlippert , Thanks a lot! I just tried pre-release of the SB Tools and syntax highlighting works flawlessly. Looking forward to official release of the SB Tools, for now staying with pre-release. |
thanks @martinlippert! |
Hi, I installed the recent release version of SBT extension, Spring Boot Tools v1.58.0, and highlighting in Java files works as before. Thanks everyone for the help and timely resolution. Vitaly |
After recent update of VS Code and Java Language Support extension(s), the highlight of the elements under cursor no longer working (please see snapshots below).
Environment
Steps To Reproduce
Current Result
Expected Result
The text was updated successfully, but these errors were encountered: