Community
Participate
Working Groups
I've upgraded my eclipse to I20070614-0800. I have platform-ui, platform-ui-examples, and platform-ui-tests checked out in my workspace, plus a test "tools" project I restart eclipse after I've closed all my editors, and use CTRL+SHIFT+T to open org.eclipse.core.internal.expressions.TestExpression which is a classfile. If I select TypeExtensionManager from one of its private static variables and hit F3 I get the status message "Current text selection does not resolve to a java element". Selecting it and using CTRL+SHIFT+T will open it no problem, but it won't participate in any of the hierarchy operations (CTRL+T, F4) although CTRL+O continues to work. PW
It seems to work in a clean workspace. Is there an index file I can delete in my old workspace? PW
I'm afraid deleting the indexes won't help. They must be okay since you can find TypeExtensionManager using Open Type. There must be some other difference in your old workspace (different preferences, another project with the same types, ...) that make the resolve fail. Any compiler errors, build path problems reported in the Problem view ? Anything in the .log ?
Created attachment 71443 [details] Log from the problem workspace In the sessions that have the problem I haven't received any errors except my keybinding conflict for F12. Those are the SESSIONs from the 14th. But in this workspace, earlier, I've had PDE parse errors, a few update URL errors, and at least one session that died with PermGen problems. PW
There aren't any errors currently in the workspace, as I've closed 2 projects (org.eclipse.ui.win32 and org.eclipse.ui.carbon) that don't compile on linux. PW
Paul, do you still have your old workspace ? Can we get a hold on it ?
Reproduced with Paul's workspace. Thanks Paul. David can you please investigate ? (ask me for Paul's workspace)
The opened TestExpression is the TestExpression on the classpath of org.eclipse.platform.doc.isv. TestExpression imports CoreException but this type is not on the classpath. An AbortCompilation occurs during parsedUnit.scope.faultInTypes() call then no results are returned. The problem is similar to bug 185319.
*** Bug 112292 has been marked as a duplicate of this bug. ***
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.