| Summary: | build-task of generated project destroys Eclipse-startup-settings (doesn't even read the settings) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Buildship | Reporter: | Thomas Schöfbeck <Yin.Yang> | ||||||
| Component: | General | Assignee: | Simon Scholz <simon.scholz> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | csdonat, etienne, istewart | ||||||
| Version: | 1.0.2 | ||||||||
| Target Milestone: | 1.0.5 | ||||||||
| Hardware: | PC | ||||||||
| OS: | All | ||||||||
| Whiteboard: | bug | ||||||||
| Bug Depends on: | 478054 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Created attachment 256362 [details]
EventDetails for FrameworkEvent error
FYI: this is the first error that occurs after the Eclipse-restart:
Root exception:
java.lang.IllegalStateException: Workbench has not been created yet.
Hi Thomas, Thanks for the bug report. I've looked into this, and it seems to be pretty peculiar. By following your steps, I can reproduce behaviour similar to yours. The first time I was able to reproduce some kind of an error, I was in the same workspace, but the java/gradle projects weren't picked up by Eclipse. I could create new projects, but those old projects wouldn't persist. The second time (current attempt) I can no longer even start Eclipse, I get an error here: !ENTRY org.eclipse.osgi 4 0 2015-09-04 11:59:55.182 !MESSAGE Application error !STACK 1 org.eclipse.swt.SWTError: Not implemented [multiple displays] This error follows the FrameworkEvent ERROR. At this point, I'm not certain what the solution is, but I can confirm that I can reproduce behaviour similar to yours by following your steps. Thanks, Ian Created attachment 256392 [details]
Current Log
This is my current log file.
Hello I just followed your steps (thanks for the precise use case) and cannot reproduce this any more with the latest 1.0.5 Buildship version. It seems that your issue is similar to the one in Bug 478054. Can you please verify this. Thank you Hi Simon, as written in the forum yesterday, your fix for Bug 478054 - included in the 1.04-snapshot as well as v1.05 - fixed also my issue here (the bug was created with v1.02, don't know who changed the version to 1.05 here). @Ian: since you had a slightly different behaviour: Does it work now for you also? Regards, Thomas One "off-topic"-question: How are versions handled here? I Can't find releases (except 1.0.0), or tags on github. @Thomas: I created tags for our existing releases on GitHub and ensured that the tags will be created automatically in the future. |
If you create s new gradle-project, run the 'build'-task and then restart Eclipse, you don't have a chance to get to your default-workspace by default - no matter if you try to check the "Prompt for workspace on startup"-option in the startup-preferences, or if you try to change the settings directly in the 'org.eclipse.ui.ide.prefs'-file it gets completely ignored. How i reproduced it: 1.) ensure a clean Eclipse-installation (delete .eclipse, .p2 and workspace in the <user-dir>) 2.) Install Eclipse-Mars new (i deleted the old inst.-dir & ectracted the zip) 3.) During startup, select a new, empty dir as the new default-workspace 4.) create a new Java-Project (just to verify in which workspace you are, setting the "Show workspace path in window title" would do it also, but this setting gets also reset after the gradle-build & Eclipse-restart) 5.) Install Buildship (did it via Marketplace) 6.) Create a Gradle project - here the Eclispe-restart is still correct 7.) Run the 'build'-task (it runs without showing any errors) 8.) Restart Eclipse: Now you are suddenly in the <userdir>- instead of your default-workspace. You are able to switch to your default-workspace, but after a Eclipse-restart you are again in the <userdir>-workspace, no matter what you try via the preferences or the 'org.eclipse.ui.ide.prefs' (the values in there are still correct it just ssems not be read by Eclipse anymore) Regards, Thomas