Community
Participate
Working Groups
this appeared in my console window (NOT IN THE LOG). Don't know how it got there: ---------------------------------- java.lang.ClassCastException at org.eclipse.jdt.internal.core.util.HandleFactory$1$Visitor.visit(Hand leFactory.java:245) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDe claration.java:1083) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDe claration.java:1006) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.trav erse(CompilationUnitDeclaration.java:305) at org.eclipse.jdt.internal.core.util.HandleFactory.createElement(Handle Factory.java:292) at org.eclipse.jdt.internal.core.SelectionRequestor.acceptLocalVariable( SelectionRequestor.java:191) at org.eclipse.jdt.internal.codeassist.SelectionEngine.selectFrom(Select ionEngine.java:650) at org.eclipse.jdt.internal.codeassist.SelectionEngine.select(SelectionE ngine.java:520) at org.eclipse.jdt.internal.core.Openable.codeSelect(Openable.java:169) at org.eclipse.jdt.internal.core.ClassFile.codeSelect(ClassFile.java:134 ) at org.eclipse.jdt.internal.core.ClassFile.codeSelect(ClassFile.java:119 ) at org.eclipse.jdt.internal.ui.text.java.hover.AbstractJavaEditorTextHov er.getHoverInfo(AbstractJavaEditorTextHover.java:95) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverIn fo(BestMatchHover.java:140) at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy. getHoverInfo(JavaEditorTextHoverProxy.java:69) at org.eclipse.jface.text.TextViewerHoverManager$2.run(TextViewerHoverMa nager.java:119)
I200311260800
Which build are you using ?
look at comment 1
Frederic - seems like the problem you addressed earlier this week.
I agree that this look the same, but without any test case it is hard to be 100% sure of that... Nikolay, please verify that it is fixed with a build > 20031201
this has only happend once to me and I have no idea how. I just logged the stack trace and hoped it was enough info for you guys to go on.
Reopen to change state result from FIXED to DUPLICATE
As there was no code modification, it's better to use DUPLICATE for result state. It's also give a little idea of what was the similar problem... *** This bug has been marked as a duplicate of 47177 ***
As David rightly said, it's not possible that this bug was a duplicate of bug 47177 as it appeared post M5...
This problem surely should have been fixed while Handlefactory rewriting (see bug 47214). Just let us know if this assumption would not be correct
Timed out
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
