Please provide
And a thorough description of the problem / question:
After update of SonarQube for Eclipse from 12.7 to 12.8 Eclipse won’t start.
Attaching the crash log.
eclipseStartupCrashLog.zip (14.4 KB)
Hey @lrozenblyum, thanks for reaching out.
I think this is not a SonarQube for Eclipse crash. Eclipse 2026-06 itself never reaches the workbench because two versions of ASM are installed at the same time: 9.9.1 (I think this is what 2026-06 ships) and 9.10.1.
OSGi cannot resolve SPIFly, SVG/SWT fails, and startup ends with Application "org.eclipse.ui.ide.workbench" could not be found. SonarQube for Eclipse 12.8 probably fails only as a side effect.
Would you be able to investigate and see if you have multiple asm versions/jars under eclipse/plugins?
Hey @lrozenblyum,
Have you updated the plug-in from the Eclipse Marketplace? I had the same issue with other plug-ins installed from it, so I would also assume the issue is not related to SonarQube for Eclipse.
I do not have that issue with my installation of Eclipse 2026-03 and 2026-09; therefore, I would highly advise updating your Eclipse installation, as it seems only that version is affected.
Cheers 
Hi, @nicolas.quinquenel I reinstalled Eclipse 2026-06 from scratch and the issue hasn’t been reproduced since then (installed also the most recent SonarQube for Eclipse plug-in).
Unfortunately I don’t have the original environment to check the asm libraries.
@EclipseWizard I’ve reinstalled 2026-06, so far so good… I’ll consider upgrade to Eclipse 2026-09 but that’s another story)
Thanks @nicolas.quinquenel, your ASM hypothesis was right. This time I kept the broken install and could confirm it. It isn’t a SonarQube for Eclipse bug.
What happened (Eclipse 2026-06 / 4.40, update 12.8 → 13.0 via Check for Updates)
Some of my enabled update sites (releases/latest, epp/packages/latest, webtools/repository/latest) now serve 2026-09 content. The update session pulled in part of the ASM family at 9.10.1:
| bundle | 9.9.1 | 9.10.1 |
|---|---|---|
| org.objectweb.asm |  |
|
| org.objectweb.asm.tree | |
|
| org.objectweb.asm.commons | (only one) |
– |
| org.objectweb.asm.util | – | (only one) |
| org.objectweb.asm.tree.analysis | – | |
asm.commons stayed at 9.9.1 because org.jacoco.core 0.8.14 (EclEmma) pins it to [9.9.0,9.10.0). SpiFly 1.3.7 imports asm, asm.commons and asm.util, which now need two different ASM versions. That causes a uses-constraint violation, and the failure cascades: jsvg → org.eclipse.swt.svg → jface → workbench. The result is Application "org.eclipse.ui.ide.workbench" could not be found in the registry.
The p2 plan is valid, but OSGi can’t resolve it, because p2 doesn’t model uses constraints. The SonarQube update only triggered the session. Rolling SonarQube back to 12.8 alone didn’t fix startup.
Upstream
Recovery without reinstalling
Complete the 9.10.1 family so SpiFly can wire consistently:
eclipsec.exe -nosplash -application org.eclipse.equinox.p2.director -profile epp.package.jee -installIU org.objectweb.asm.commons/9.10.1 -repository https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/release/4.41.0/
Then start once with eclipse.exe -clean. Also disable the latest update sites on a 2026-06 install.