-
Our project contains a plugin with 2 views that fails to load in Eclipse 2024-09 M2. (I added the Samples View too if we did something wrong, that apart of the On Windows 11, the errors are logged as:
I have tried zapping all Eclipse installation plus directories I also get a few other exceptions I can't wrap my head around as shown below, and I also get this in earlier Eclipse 2024-06 GA. The plugins project are configured as "normal" plug-in projects + Java nature, nothing fancy with Maven or so.
This code has been working fine for the last 10 or more Eclipse versions, so I don't really understand what is gone wrong. Sure, we've updated the code for Java 17 some time ago, but this has been running fine since Java 17 was introduced into Eclipse (4.19 or 4.21?). All this when happens when launching a |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments
-
Can you clear the log and attach the full /.metadata/.log file here? You can delete that file before you start to reduce the log content to just the startup problems. I just wonder if there is some more helpful detail in earlier stack trace. |
Beta Was this translation helpful? Give feedback.
-
Here is the full log (cleared before launch): The strange thing is why the classes can't be loaded, would this be due to the fact that they depend on the View's that can't be created either, due to the inaccessible (or missing) |
Beta Was this translation helpful? Give feedback.
-
Do you have any clue as to how I can work-around it in e.g. older Eclipse versions, or if you could point me in the "right" direction where to look (if we've done something in our code - I know... it's a longshot)? I have tried clearing/deleting/reinstalling both Eclipse and workspaces and directories |
Beta Was this translation helpful? Give feedback.
-
Every single thing in the log appears to be trying to create an executable extension org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension where it looks for some class in some expected plugin that is supposed to provide it and simply fails to find it. I see no logged errors about bundles failing to start because of missing dependencies. No linkage errors or other runtime errors. It's really as if the bundles don't actually provide the classes. Maybe running with -clean -debug would provide information about bundles failing to start. Are you able to debug launch these from a development IDE? |
Beta Was this translation helpful? Give feedback.
-
No, when I start debugging or running, that is when it happens. So I'm in the "dark". I'll give the -debug option a try, I already have -clean. |
Beta Was this translation helpful? Give feedback.
-
Where do you specify -debug option? In Program Arguments or VM, like -Ddebug=true, or? |
Beta Was this translation helpful? Give feedback.
-
It's a program arguments box of the arguments tab Inspect what's in the Plug-ins tab. Try the Validate Plug-ins button there. I've done silly things like disable auto build and then forgetting to enable it. |
Beta Was this translation helpful? Give feedback.
-
Done that. Added -debug to pgm args - no change (strange!). I turned on most all traces too and enabled each one. Where do trace files go (I can't find this info on the net)? Eclipse Console output added below. I added the Program Arguments -debug -clearPersistedState, still same behavior. Oh, great: ends with |
Beta Was this translation helpful? Give feedback.
-
I added "-debug -clear -clearPersistedState" options to eclipse.ini (2024-09 M2 version 4.33 - BTW Eclipse Marketplace app defintion calls version 4.33 "2024-06" in error - should be "2024-09" - where do I report this?). Where are the debug files? |
Beta Was this translation helpful? Give feedback.
-
Is -consoleLog in the arguments? Then details should show in the console view. I get confused here because we talk about debug launch but then we also talk about editing the eclipse.ini which does not sound like your launching your stuff from a development IDE. |
Beta Was this translation helpful? Give feedback.
-
Well, I tried (desperately) to find a solution, so I set -debug option in Eclipse IDE itself, no change, so I removed it. The command line for launch configuration is:
Console view log attached: "same" thing... |
Beta Was this translation helpful? Give feedback.
-
This is how the started debug window of Eclipse "Committers" version with our 2 plugins looks like (pretty broken as nothing gets loaded): |
Beta Was this translation helpful? Give feedback.
-
I have converted it to a discussion for now until its clear what issue we see and if/how it relates to platform.ui, then we should created a new issue that clearly states the problem. If I look at the code I see:
So if this class either contained in the bundle (e.g. BundleClasspath set correctly (including the Next you should check that you have updated all lower bounds of dependencies to match the latest Eclipse version. Then I see
So your code seem to not properly handle OSGi services, consider using DS or ServiceTracker and add appropiate handling in the code when things are absent. Next there are several tabine specific warnings:
I can't tell if/what that means and if there are any connected problems. |
Beta Was this translation helpful? Give feedback.
I have converted it to a discussion for now until its clear what issue we see and if/how it relates to platform.ui, then we should created a new issue that clearly states the problem.
If I look at the code I see:
So if this class either contained in the bundle (e.g. BundleClasspath set correctly (including the
.
) or properly imported (e.g. not transitively or optional)?Next you should check that you have updated all lower bounds of dependenc…