| Summary: | An internal error occurred during: "Launching ???" | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Frank Becker <eclipse> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtis.windatt.public, tjwatson |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Frank Becker
So you have 3 workspaces? 1) Host workspace with the Mylyn bundles in your workspace 2) A runtime workbench launched from (1) also with the Mylyn bundles in that workspace 3) A runtime workbench launched from (2) While ConfiguratorUtils is deprecated, it still exists in 3.7RC3. I suspect that when you launch runtime workbench (2), you are not including update configurator, but when launching (3) you are including update configurator. If update.configurator is included in a launch, PDE uses ConfiguratorUtils from update.configurator to create a platform.xml. What is odd here is that if update.configurator was not available, I would have expected the PDE bundles to not start due to the missing dependency. Can you please try to come up with steps to reproduce? (In reply to comment #1) > So you have 3 workspaces? > > 1) Host workspace with the Mylyn bundles in your workspace > 2) A runtime workbench launched from (1) also with the Mylyn bundles in that > workspace > 3) A runtime workbench launched from (2) > > While ConfiguratorUtils is deprecated, it still exists in 3.7RC3. I suspect > that when you launch runtime workbench (2), you are not including update > configurator, but when launching (3) you are including update configurator. If > update.configurator is included in a launch, PDE uses ConfiguratorUtils from > update.configurator to create a platform.xml. What is odd here is that if > update.configurator was not available, I would have expected the PDE bundles to > not start due to the missing dependency. > > Can you please try to come up with steps to reproduce? Sorry I can not reproduce this . But the same happens three times in the last two weeks (3.7.RC1 -RC3). I saw this after I had worked several times with my 3 workspaces. Maybe this is related to an problem shutting down my computer. I know that the problem must be related to my Host workspace where I have set the the Target Platform to mylyn-e3.7. Actual I have two versions of my Host workspace (Space 500MB). One that has the error and an working on. If you want I can try to replace some files in the .metadata I think I have found the reason for this problem. The Target Platform mylyn-e3.7 use http://download.eclipse.org/eclipse/updates/3.7milestones/ for the Eclipse SDK. When using this you get Version: 3.7.0 Build id: I20100805-1700 where I get the error. When I use <location path="${eclipse_home}" type="Profile"/> everything is fine. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. (In reply to Eclipse Genie from comment #4) > This bug hasn't had any activity in quite some time. Maybe the problem got > resolved, was a duplicate of something else, or became less pressing for > some reason - or maybe it's still relevant but just hasn't been looked at > yet. > > If you have further information on the current state of the bug, please add > it. The information can be, for example, that the problem still occurs, that > you still want the feature, that more information is needed, or that the bug > is (for whatever reason) no longer relevant. > > -- > The automated Eclipse Genie. Maybe we can close this bug. Now we use OOMPH for the setup. This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag. This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag. |