Community
Participate
Working Groups
Since the update to Eclipse 4.23 launch configurations from previous Eclipse versions fail to start. The error log shows following exception: ``` java.util.NoSuchElementException: No value present at java.base/java.util.Optional.orElseThrow(Optional.java:377) at org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper.getSelectedModels(BundleLauncherHelper.java:409) at org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper.getBundleMap(BundleLauncherHelper.java:391) at org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper.getWorkspaceBundleMap(BundleLauncherHelper.java:354) at org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper.getWorkspaceBundleMap(BundleLauncherHelper.java:69) at org.eclipse.pde.internal.launching.launcher.LaunchPluginValidator.getSelectedWorkspacePlugins(LaunchPluginValidator.java:42) at org.eclipse.pde.internal.launching.launcher.LaunchPluginValidator.getAffectedProjects(LaunchPluginValidator.java:63) at org.eclipse.pde.internal.launching.launcher.LaunchPluginValidator.getAffectedProjects(LaunchPluginValidator.java:51) at org.eclipse.pde.launching.AbstractPDELaunchConfiguration.getBuildOrder(AbstractPDELaunchConfiguration.java:422) at org.eclipse.debug.core.model.LaunchConfigurationDelegate.saveBeforeLaunch(LaunchConfigurationDelegate.java:244) at org.eclipse.debug.core.model.LaunchConfigurationDelegate.preLaunchCheck(LaunchConfigurationDelegate.java:197) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:767) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:716) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1021) at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1224) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) ```
Benjamin, that could be if you use bundles from the running platform or mix bundles from your current target platform with the new running platform. Please inspect your target platforms and the bundles used in your run configuration. Run configurations are not automatically compatible.
There's a designated target platform which should not interfere with the running one. The launch configuration is containing no additional bundles, but only features defined in the workspace.
Did you try to clean your runtime workspace and runtime configuration area?
Haven't tried that before. However the exception is thrown before the cleaning confirmation dialog is able to pop up.
(In reply to Benjamin Brandl from comment #4) > Haven't tried that before. However the exception is thrown before the > cleaning confirmation dialog is able to pop up. I see, maybe your eclipse is stale. Please try to run your eclipse with eclipse.exe -clean To also reset the UI model you can run with eclipse.exe -clearPersistedState
Unfortunately both arguments don't have an effect. Previous launch configuration fail to run the underlying product. My workaround is to recreate the configurations. So it's only a backwards compatibility issue. Still, I'm a little bit surprised as I haven't seen such thing in years. Interestingly the issue didn't appear in 4.23 milestones and release candidates. It only appeared in the released version, here in the updated instance as well as in an new one.
I've compared the newly create launch configuration with a failing one: The new one doesn't have the `setAttribute` `selected_target_bundles` and `select_workspace_bundles`. If I remove the `<setAttribute key="select_workspace_bundles">` from a failing configuration, it will start again. So that's what the `BundleLauncherHelper.getWorkspaceBundleMap` in the stack trace is referring to.
I bumped into this one also. After some testing I found out that some plugins lacked "@default:default" in the <setEntry> tag. After adding that the application started normal.
