Community
Participate
Working Groups
I tried to start an existing run configuration but getting: org.eclipse.e4.core.di.InjectionException: Unable to process "EclipseAdapter.null": no actual value was found for the argument "String[@javax.inject.Named(value="e4.internal.injectionLink")]". at org.eclipse.e4.core.internal.di.InjectorImpl.reportUnresolvedArgument(InjectorImpl.java:478) at org.eclipse.e4.core.internal.di.InjectorImpl.resolveRequestorArgs(InjectorImpl.java:469) at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:129) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:403) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:330) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:202) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:481) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:495) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:213) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:573) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596) at org.eclipse.equinox.launcher.Main.run(Main.java:1467) at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
Strange enough the only reference in the code seems to be: @Optional @Named("e4.internal.injectionLink") final static public String pseudoVariable = null; so it is marked as optional. What makes me wonder is: a) it is a static field b) it is marked as final c) the class was changed over 2 years ago so maybe something has changed inside e4 that prevents such fields from being injected and the error message is just wrong here? I updated to the current I builds but problem still persists. As this is a plugin based launch, might it be related to the recent changes in PDE runtime computation @Hannes?
"e4.internal.injectionLink" is not a context variable I know of. You can use the context spy to see what is available for di
(In reply to Lars Vogel from comment #2) > "e4.internal.injectionLink" is not a context variable I know of. You can use > the context spy to see what is available for di Maybe yes, if the Eclipse IDE Application would actually start ;-) You can search the platform classes for "e4.internal.injectionLink" to find it...
(In reply to Christoph Laeubrich from comment #1) > > I updated to the current I builds but problem still persists. As this is a > plugin based launch, might it be related to the recent changes in PDE > runtime computation @Hannes? Hard to tell, without the Launch-Config and without TP respectivly the workspace plug-ins. But for plug-in based launches actually only the handling of multiple versions of the same bundle were made more precise. So as long as you did not have multiple versions of a plug-in in your workspace it should not have changed. But if you have an old Version of the launching eclipse available you could compare the configuration/org.eclipse.equinox.simpleconfigurator/bundles.info file of the launched application with new and old version. If there is a related difference it would indeed be interesting to know.
(In reply to Hannes Wellmann from comment #4) > (In reply to Christoph Laeubrich from comment #1) > > > > I updated to the current I builds but problem still persists. As this is a > > plugin based launch, might it be related to the recent changes in PDE > > runtime computation @Hannes? > > Hard to tell, without the Launch-Config and without TP respectivly the > workspace plug-ins. But for plug-in based launches actually only the > handling of multiple versions of the same bundle were made more precise. So > as long as you did not have multiple versions of a plug-in in your workspace > it should not have changed. > > But if you have an old Version of the launching eclipse available you could > compare the > configuration/org.eclipse.equinox.simpleconfigurator/bundles.info file of > the launched application with new and old version. If there is a related > difference it would indeed be interesting to know. I'm using https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning and using the "Runtime Workspace" Launch config.
(In reply to Christoph Laeubrich from comment #5) > I'm using https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning and > using the "Runtime Workspace" Launch config. The linked configuration unfortunately fails on my computer... In which repo is it located? But in general I have the impression that some launch-configurations become outdated. Have you successfully launched that config before? If not I would assume that it was broken before.
(In reply to Hannes Wellmann from comment #6) > (In reply to Christoph Laeubrich from comment #5) > > I'm using https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning and > > using the "Runtime Workspace" Launch config. > > The linked configuration unfortunately fails on my computer... The Launch Config? That's what this bug is about ;-) > In which repo is it located? Don't know... > But in general I have the impression that some launch-configurations become > outdated. Have you successfully launched that config before? If not I would > assume that it was broken before. Yes I'm using this for my regular for development of platform code.
(In reply to Christoph Laeubrich from comment #7) > (In reply to Hannes Wellmann from comment #6) > > (In reply to Christoph Laeubrich from comment #5) > > > I'm using https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning and > > > using the "Runtime Workspace" Launch config. > > > > The linked configuration unfortunately fails on my computer... > > The Launch Config? That's what this bug is about ;-) The Oomph Setup Configuration, sorry that was not clear. > > > > In which repo is it located? > > Don't know... Doesn't the Common tab of the Run configurations wizard show you the workspace project the launch-config is located in? From this the git-repo should be clear. > > But in general I have the impression that some launch-configurations become > > outdated. Have you successfully launched that config before? If not I would > > assume that it was broken before. > > Yes I'm using this for my regular for development of platform code. That would have been too easy^^
I 'fixed' the Problem by a complete reinstall according to https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning
