Eclipse fails to start after updating Copilot from 0.19.0 to 0.21.0 on Pleiades 2026-06 due to ASM version conflict · Issue #474 · microsoft/copilot-for-eclipse · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Eclipse fails to start after updating Copilot from 0.19.0 to 0.21.0 on Pleiades 2026-06 due to ASM version conflict #474
After updating GitHub Copilot for Eclipse from version 0.19.0 to
0.21.0, Eclipse fails to start.
Environment:
Pleiades All in One 2026-06 Java Full Edition
Eclipse 4.40.0.20260604-0652
Java 21.0.11
Windows x86_64
GitHub Copilot before update: 0.19.0
GitHub Copilot after update: 0.21.0
The issue is reproducible even after deleting the existing Pleiades
installation and performing a clean installation.
The Eclipse log reports an OSGi uses constraint violation caused by
the coexistence of the following ASM bundles:
org.objectweb.asm 9.9.1
org.objectweb.asm 9.10.1
org.objectweb.asm.util 9.10.1
Representative error:
Uses constraint violation. Unable to resolve resource
org.apache.aries.spifly.dynamic.bundle because it is exposed to
package 'org.objectweb.asm' from resources org.objectweb.asm 9.9.1
and org.objectweb.asm 9.10.1 via two dependency chains.
Pleiades 2026-06 includes GitHub Copilot 0.19.0 by default.
Eclipse starts successfully with that version. However, after
updating GitHub Copilot to 0.21.0 from the official update site and
restarting Eclipse, Eclipse no longer starts.
Could you please confirm whether GitHub Copilot 0.21.0 supports
Eclipse 4.40 and Pleiades 2026-06?
Could you also check whether the ASM dependencies installed or
updated with GitHub Copilot can be aligned to avoid this conflict?
I can provide the complete Eclipse error log if needed.
Activity