IDE name and version: Eclipse Version: 2024-09 (4.33.0) Build id: 20240905-0614
SonarQube for Eclipse plugin version: 11.21.0.84299
Programming language you’re coding in: Java
Is connected mode used:
SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): SonarQube Community Build v25.9.0.112764
And a thorough description of the problem / question:
Every time I modify and save a .java/.xml file with Eclipse, being the Run SonarQube automatically enabled in that Project, it causes a corruption, that’s visible when I try, later, to do any SCM operation that involves that file (SVN/Git Revert, Commit, Update to HEAD, whatever).
I’ve been experiencing this issue since we moved to v11 of the plugin, a few months ago, due to upgrading to a supported SonarQube Community version and we needed to make work Connected Mode against our instance.
We’ve had to disable this checkbox, because it’s broking our projects with a relatively high frequency.
I don’t know if any other people is experiencing this, because I´ve searched a bit in the forums, but I hadn’t find any coincidence with this issue.
Hope you can help me/us, because it’s rather a pain.
Can you please provide logs for that issue? Also, please elaborate on what kind of visible corruption you mean (maybe you have a screenshot if it is something in the UI?).
Sure, sorry, I’ll provide the error it’s shown on the SVN Console
I’ll provide you with context, as I said before, we get this error just after modifying a Java/XML file in a project under SCM control, saving it, (with the checkbox of Run SonarQube automatically enabled in that project’s properties), and trying to perform an SCM action, (like Revert, in this example), causes to break and leaving that SCM’s metadata corrupted and in need to perform an SVN Cleanup (in the case of SVN), to get it working again.
Here it is:
revert C:/eclipse/$PROJECT_NAME
Reverted C:/eclipse/$PROJECT_NAME/Eco.java
Problem running log
svn: Failed to run the WC DB work queue associated with ‘C:\eclipse\$PROJECT_NAME’, work item 16 (file-install $PROJECT_NAME/Eco.java 1 0 1 1)
Acceso denegado.
svn: Can’t move ‘C:\eclipse\$PROJECT_NAME\.svn\tmp\svn-A3603DC’ to ‘C:\eclipse\$PROJECT_NAME\Eco.java’: Acceso denegado.
Additional errors:
Problem running log
svn: Failed to run the WC DB work queue associated with ‘C:\eclipse\$PROJECT_NAME’, work item 16 (file-install $PROJECT_NAME/Eco.java 1 0 1 1)
Acceso denegado.
svn: Can’t move ‘C:\eclipse\$PROJECT_NAME\.svn\tmp\svn-BBA33E9’ to ‘C:\eclipse\Eco.java’: Acceso denegado.
If you need any more information/details, please, just ask
I have a guess here, handing it over to the experts at Sonar:
There is no Integration with SVN in the Plugin or any of the analyzers, I only can guess here that the files are blocked by the analyzers After changes are applied (and the Automatik analysis Starts) prohibiting SVN from Doing its shenanigans.
I‘m working with Git and I have not yet encountered a similar issue. Being it a Small Code base or a huge One where analysis takes some time on a Single file leaving time to do Git actions.
if you reproduce it, could you also please provide the logs of the SonarQube Console? Also any entries in the Error Log view might be helpful.
And yes, the topic will be triaged at Sonar, please bear with them
Ok, after a few more testing, I can tell the issue is only happening when in Connected Mode, tried a few times and it only happens when it’s on Connected Mode.
Yeah, I was able to reproduce it, so I can provide the logs of the SonarQube Console, as you ask.
I just checked the Error Log view and it shows a few ones, but nothing from the SonarQube for IDE plugin, so I guess it’s not that helpful for this case, right?
I’ll DM you with the log (SonarQube Console), if you don’t have problem with that, due to confidentiality reasons.
Please wait for someone from Sonar to reach out to you regarding the logs. I’m not working at Sonar
I’m just very familiar with the Eclipse Plug-in and helping here as a fellow Community user ^^
But thank you for some more testing and tinkering around to find the cause; everything will be helpful to them.
Sorry, but just remembering that we’ve got this frozen…
We’re more than ready to collaborate giving info about the issue so we can help Sonar team to fix it, we just need the support from someone from the team
@Takuya I have sent you a DM so that you can share private information to help us to get to the bottom of this. However, I encourage you to keep the general conversation going on here in case anybody else would be looking for the same issue.
You mentioned that it happened with Java/XML files. Did you try other extensions and they are ok or the issue seems specific to these?
Yeah, thanks, we’ll keep the conversation there, but for sure, I’ll keep this thread/post with activity when we discover more or reach the solution to this issue
The only thing is that I’ll take on holidays from today till end January 2026, so could it be possible to keep it open even without activity for 1 month or so? As soon as I get back to my job, I’ll check this out and answer if there’s been any updates/news, for sure.
You mentioned that it happened with Java/XML files. Did you try other extensions and they are ok or the issue seems specific to these?
Related to this, it seems to happen only with these 2 type of files, because I tried it with .groovy files & .txt and no issues so far with them. Maybe it’s because SonarQube for IDE doesn’t auto analyze those type of files, I don’t know.
Thank you very much for your DM and reply here, hope we can reach to a solution together
And thank you EclipseWizard (seems I can’t mention you due to being a new user) too !!
Unfortunately, I can’t share much progress. I’ve tried with SVN on my Linux machine and still fail to reproduce. Next step will be to ask somebody with Windows to try, in case the issue is platform-specific.
On a side note, we are also making some effort to make sure we don’t leave analyzed files opened in general. It should be in one of the next few releases.
By the way, we did merge something for proper file closing a few releases ago, it should be since eclipse plugin version 11.22.0.84372. You mentioned just previous version in the initial post. Just to double check, have you tried new version since? Because was trying to reproduce at the last one.
,
!!