New markers in Eclipse SonarQube for IDE

Hello,

In the newest version of Eclipse SonarQube for IDE, red rectangles related to a task “text to be deleted” have appeared.

import java.util.List;

public class TestSonar {

	boolean isEmpty(List l) {
		return l == null || l.size() == 0;
	}
}

I think this is unnecessary visual pollution as we have already everything we need with the blue markers.

More concerning, the red marker does not disappear after the quick fix is applied.

Version info:

Eclipse IDE for Java Developers (includes Incubating components)

Version: 2026-03 (4.39.0)

Build id: 20260305-0817

SonarLint for Eclipse 12.1.0.84656 org.sonarlint.eclipse.feature.feature.group SonarSource

Thanks & regards,

Nicolas Baumann.

Hey @Nicolas_Baumann,

There is no new marker with SonarQube for IDE. Can it be that you perhaps also have the GitHub Copilot plug-in installed?
There is a similar thread, and I guess this can be the same root cause:

You’re probably right. But the rectangles are shaped around the sonar locations, which is misleading.

Thanks for reporting this, we will have a look!

@EclipseWizard SonarQube QuickFixes have no marker annotations. I wonder if this could lead to a fallback on such markers?

The issue is not on SonarQube side but in copilot plugin for eclipse.

Yes, there’s a conflict with the Copilot plugin that we identified in the other thread, but we’re still looking at a workaround that would avoid such conflicts. The current next steps I see:

  • Define a proper marker annotation in the SonarQube for Eclipse plugin, that would avoid such unwanted overrides
  • Report the bad citizenship to GH Copilot for Eclipse

We will iterate on this and let you know as soon as we have a proper fix.

I guess it could. I can also not recall what the reason is for them not having some marker annotations. Maybe ask good ol’ JH why this wasn’t implemented, I think he may have an answer for that.

I encountered it as well when I was checking the other thread, but as I’m not using the Copilot plug-in and only fiddled around with it I didn’t go into full debug mode :smiley:

Cheers :beer_mug:

Hey! I reported the issue on Copilot for Eclipse side, and they have fixed it. The fix should be included in their next release.

Hello @nicolas.quinquenel , based on this comment [Bug] Eclipse red border annotations persist for SonarQube issue locations and conflict with Copilot NES delete annotations · Issue #23 · microsoft/copilot-for-eclipse · GitHub I may assume SonarQube Lint is also implementing a fix for this issue, right? Asking that because SonarQube Lint has a more frequent release cadence than GitHub CoPilot thus we may benefit from the fix earlier (pretty annoying issue…)

Hey @lrozenblyum, Copilot for Eclipse has released version 0.17 that contains the fix. This should solve the problem.

Unfortunately, we haven’t had the bandwidth to tackle this on our side due to current priorities. Since the issue has now been fixed on the Copilot side, we no longer consider it urgent.

Let us know if you still notice any problems, thanks!

Thanks @nicolas.quinquenel - at the moment the combination of SonarQube in Eclipse and Copilot for Eclipse work fine.