Bug 54290 - An internal error occurred during: "Java AST creation".
Summary: An internal error occurred during: "Java AST creation".
Status: RESOLVED DUPLICATE of bug 53357
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-10 09:54 EST by John P. A. Verhaeg CLA
Modified: 2004-03-11 08:50 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John P. A. Verhaeg CLA 2004-03-10 09:54:24 EST 
I just started getting this today when I right-click on a class name or hit F3 
to navigate to it.  I've been using M7 for about a week now, but this is the 
first I've seen of this:

org.eclipse.jdt.internal.compiler.problem.AbortCompilation
at org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle
(ProblemHandler.java:94)
at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle
(ProblemReporter.java:1034)
at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.isClassPathCorrect
(ProblemReporter.java:2110)
at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve
(UnresolvedReferenceBinding.java:37)
at org.eclipse.jdt.internal.compiler.lookup.PackageBinding.getTypeOrPackage
(PackageBinding.java:163)
at org.eclipse.jdt.internal.compiler.lookup.Scope.getTypeOrPackage
(Scope.java:1467)
at org.eclipse.jdt.core.dom.DefaultBindingResolver.resolveName
(DefaultBindingResolver.java:228)
at org.eclipse.jdt.core.dom.Name.resolveBinding(Name.java:89)
at org.eclipse.jdt.internal.ui.search.OccurrencesFinder.visit
(OccurrencesFinder.java:147)
at org.eclipse.jdt.core.dom.QualifiedName.accept0(QualifiedName.java:88)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1409)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:1456)
at org.eclipse.jdt.core.dom.ImportDeclaration.accept0
(ImportDeclaration.java:84)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1409)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:1479)
at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:165)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:1409)
at org.eclipse.jdt.internal.ui.search.OccurrencesFinder.perform
(OccurrencesFinder.java:73)
at 
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.updateOccurrenceAnnotations
(JavaEditor.java:2844)
at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$5.selectionChanged
(JavaEditor.java:2868)
at 
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartLis
tenerGroup.calculateASTandInform(SelectionListenerWithASTManager.java:149)
at 
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$1.run
(SelectionListenerWithASTManager.java:99)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
Comment 1 Olivier Thomann CLA 2004-03-10 22:57:01 EST 
Close as duplicate of bug 53357.
Please use latest integration build and check if this fixed your problem.
Are you using external jars?

*** This bug has been marked as a duplicate of 53357 ***
Comment 2 John P. A. Verhaeg CLA 2004-03-11 08:50:34 EST 
I'm not using external jars.