Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Eclipse fails to start after updating Copilot from 0.19.0 to 0.21.0 on Pleiades 2026-06 due to ASM version conflict

Open
  • Is something wrong?
#474 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
devtools

Research direction

Start by comparing the ASM bundle versions in Pleiades before and after updating Copilot, using the OSGi uses-constraint error in the Eclipse log as the lead. Ask for the complete error log if needed to trace the two dependency chains. Done means identifying whether Eclipse 4.40 and Pleiades 2026-06 are supported and whether the conflicting ASM dependencies can be aligned.

Written by the indexing model from the issue text.

Description

bug

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.

Dominant language
Java
Stars
125
Forks
63
Avg merge
1d 3h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/copilot-for-eclipse

All issues in microsoft/copilot-for-eclipse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.