Replies: 2 comments 8 replies
-
|
There is a check that was implemented quite some time ago (by @mickaelistria) but I don't recall the exact details off the top of my head. Of course we have the exact same problem with the IDE package when we hit a release cycle where the bundles start using a higher BREE. I'll investigate and get back to you with the details. Products do typically specify this in the eclipse.ini
|
Beta Was this translation helpful? Give feedback.
-
|
Just as a hint, I think you have upgrade for a purpose and you are using platform API. So the best way to prevent "silent failure" is to update the lower bounds of your dependencies to match those of when platform introduced Java 17 requirements. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
I have an Eclipse plug-in (build using Tycho) whose
Bundle-RequiredExecutionEnvironmentneeds to be bumped fromJavaSE-11to (finally!)JavaSE-17. Alas, I am struggling a bit with the update's UX:Someone running an old version of the Eclipse IDE on Java 11 (this means 2022-06 or older, as newer versions already require Java 17) can install the plug-in without any error or warning that the plug-in requires a newer Java version, only to find that the plug-in's bundles don't resolve. As this means that the plug-in's UI contributions simply vanish, this problem is really hard to diagnose, unless you know about the OSGi console, bundle states, and the
diagcommand.Do old versions of p2 (e.g., those shipping in the Eclipse IDE 2022-06) simply not check for a compatible Java execution environment prior to installation? Or am I doing something wrong and need to declare my plug-in's requirement somewhere else beyond the bundle's
MANIFEST.MF?Beta Was this translation helpful? Give feedback.
All reactions