Bugzilla – Full Text Bug Listing
| Summary: | Can't run exiting run configuration | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Christoph Laeubrich <laeubi> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Lars.Vogel, wellmann.hannes1 |
| Version: | 4.22 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Christoph Laeubrich
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 |