[platform-dev] Fwd: [eclipse-packaging/packages] Eclipse 2025-06 fails t

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi folks,

Please see below and let me know your thoughts.

Thanks

Jonah

~~~
Jonah Graham (he/him)
Kichwa Coders
www.kichwacoders.com

---------- Forwarded message ---------
From: Jonah Graham <notifications@xxxxxxxxxx>
Date: Wed, 21 May 2025 at 22:19
Subject: [eclipse-packaging/packages] Eclipse 2025-06 fails to start if CodeTogether's devstyle Darkest Dark theme is installed (Issue #310)
To: eclipse-packaging/packages <packages@xxxxxxxxxxxxxxxxxx>
Cc: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>, Your activity <your_activity@xxxxxxxxxxxxxxxxxx>

jonahgraham created an issue (eclipse-packaging/packages#310)

This is a more suitable location to discuss the issues raised in eclipse-cdt/cdt#1164 - here is just a summary.

If you install devstyle Darkest Dark theme in Eclipse IDE 2025-06 the IDE will fail to start due to some byte-code manipulation that the plug-in does that breaks Eclipse startup.

While this problem is not a bug in Eclipse or its projects, the theme is one of the most popular plug-ins on the Eclipse marketplace, with probably 10s of thousands of installs that will be broken if they updated to latest Eclipse release in June. Therefore the damage to Eclipse's users will be large.

Therefore we will need to figure out how to mitigate this for our users. I have reached out to genuitec (see emails in eclipse-cdt/cdt#1164) but as of now they have not proposed a solution and there is very little time to resolve this.

Possible ways forward are:

1. Revert changes in Eclipse Platform that expose devstyle bug.
   This is undesirable as it is not obvious exactly how widespread these reversions may have to be, not how long Eclipse non-API would be held back.
2. Make Eclipse more resiliant to such changes.
   I don't know if this is feasible, the way that devstyle is byte manipulating and weaving seems very difficult to insulate against
3. Publicizing campaign.
   We can just try to publicize this, but the workaround for users if they end up with a broken install is non-trivial to do. Since the IDE won't start you can't simply undo the faulty install. The reality is that most people won't pay attention until they have a broken IDE
4. Add negative p2 requirements preventing the problematic versions of devstyle from being installed at the same time as Eclipse 2025-06.
   this will prevent users from installing specific version of devstyle into 2025-06, or prevent Eclipse 2025-03 with devstyle installed from upgrading to 2025-06. The p2 UI here isn't particularly clear as to why the install is being prevented

I solicit input from the community on what to do here. There is not much time to resolve this, if any change needs to be made in Eclipse Platform we have less than 1 week to come up with a solution.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <eclipse-packaging/packages/issues/310@github.com>