SonarQube for Eclipse plugin version: 11.24.0.84421
Programming language you’re coding in: Java + javascript/typescript (Angular)
Is connected mode used: Yes
SonarQube Server Community Build v25.12.0.11709
SonarQube server issues are shown in Eclipse code editor with red borders around. When the SQ issue is fixed in the code, the red borders won´t disappear. Coding becomes really frustrating with this feature, especially when there are multiple SQ issue in the same file.
As an attachment a image showing red borders after “Unexpected negated condition.“ SQ issue has been fixed in the TS file.
SonarQube for Eclipse plugin version: 11.25.0.84457
Programming language you’re coding in: Java
Is connected mode used: No
I have to restart Eclipse to get rid of the red borders for resolved issues.
Is there a way to not have the red borders at all? I find the underlining sufficient.
I have the same/a very similar problem: The red issue detail borders (like “+1” on if/else statements for complexity counts) along with the annotations in the border are always shown. E.g, the box around the if here:
When I select “Show issue locations”, I will get the additional issue information shown with the box, and that information is hidden again when selecting “Hide issue locations”; but the red box and the border annotation stay all the time.
This is Eclipse 2025-12 on Windows 11 with version 11.26 of the plug-in. I’m using the “Darkest Dark theme from DevStyle”-plug-in, but the problem persists when switching to Eclipse’s own styles.
thank you all for bringing up the topic, my apologies for the delayed reply. It seems to be something specific to Eclipse 2025-12, I am actively taking a look into it. I’ll keep you posted with the progress as soon as I have more updates.
I was trying to reproduce the issue, initially on Eclipse for Java 2025-12 but without success. Then 2024-12, and two other Eclipse flavors 2025-12 with combinations of connected/standalone mode and different rules but still the same
By the screenshots and your messages it seems quite a frustrating experience. I would need your help on that.
Could you please let me know:
Did the issue first appear on a fresh installation of Eclipse and/or SQEclipse?
Are there are any other extensions that could possibly conflict or interfere with the highlighting?
Do you get any exceptions or errors on the SonarQube for Eclipse logs?
Additionally, it may be helpful if you could attach the full verbose SonarQube for Eclipse logs. In the meantime, I’ll dig deeper into the code.
Fresh installation of Eclipse type “Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components)“ version 2025-12.
Of course the code project where the symptoms happen is old (over 10 years of coding). It is a Gradle project using version 9.3.1. Only installed plugins via Eclipse Marketplace: GitHub Copilot version 0.15.0.202601270459, SonarLint for Eclipse 11.26.0.84482
Thank you for looking into this. Following your reply, I retraced my steps from a couple of weeks ago when I tried to get rid of the problem with a brand-new installation: Downloaded the “Eclipse IDE for Java Developers” package, installed Lombok and a couple of plugins, imported my Maven project into a brand-new workspace …
… and I am very happy (yet also slightly confused) to say that the problem does not show up with this new installation of Eclipse: The issue location markers are shown and hidden as expected.
I can still reproduce the problem with my previous installation of Eclipse in this brand-new workspace, and vice versa: The problem does not occur in an old workspace when using the new Eclipse installation. I don’t see any errors or exceptions in the logs in either case.
There are still one or two differences between this Eclipse installation and the one from a couple of weeks ago which I cannot check for right now. (Notably perhaps the addition of the Github Copilot plugin.)
Update: After installing the Github Copilot plugin (version 0.15.0) and restarting Eclipse, the red markers problem has popped up again. And after uninstalling the Copilot plugin again, markers are back to normal.
I’ve the same problem. I can confirm too that I have the Github Copilot plugin too installed, like Chris said. So it seems some problem between both plugins?
I can confirm that there is some conflict between the SonarQube for IDE and the GitHub Copilot plugin. Not sure what or why yet, but the good thing is that I can reproduce and debug. Thank you for your helpful messages
