| Summary: | Eclipse restarts in a loop when I specify -clean option | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mauro Molinari <mauromol> | ||||||
| Component: | Runtime | Assignee: | platform-runtime-inbox <platform-runtime-inbox> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | remy.suen, tjwatson | ||||||
| Version: | 3.7.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 209222 [details]
Correct extract from the log
Sorry, the previous attachment was the full log, indeed. This one is an extract containing the first "iteration".
Perhaps a duplicate of bug 365722. Do you know if you have the framework extension org.codehaus.groovy.frameworkadapter installed? From your log ... Loading extension: reference:file:org.codehaus.groovy.frameworkadapter_2.6.1.xx-20120107-0800-e37.jar Indicates that you do have org.codehaus.groovy.frameworkadapter installed. I suspect this is a similar case as bug 365722. I am going to duplicate this bug to that one. *** This bug has been marked as a duplicate of bug 365722 *** Thank you Thomas and sorry for the duplicate. I searched for similar bugs in the Eclipse Platform category and didn't find any :-( |
Created attachment 209220 [details] The log produced by Eclipse when starting. If I add the "-clean" command line option, my Eclipse IDE now restarts in a loop repeatedly before asking for the workspace location and before showing the loading progress bar. I see the splash screen disappear and appear again shortly after, again and again. I'm attaching a log obtained by using -consoleLog and -debug command line switches and redirecting the output to a TXT file. I hope some information in there can be useful to track down the problem. I have no problem to run Eclipse if I remove the -clean option. And I didn't have problem to install plugins with the update manager so far. I remember this behaviour also happened to a co-worker of mine some time ago (with Eclipse 3.6 I think). NOTE about the attached log: this is the first "iteration" of the log. The complete log (obtained before I killed Eclipse through program manager) is a repetition of the attached one.