setProject() fehlt bei ASTParser — Bindings können null sein #49
Labels
No labels
bug
build
enhancement
headless
P1-critical
P2-high
P3-medium
P4-low
refactoring
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-tools/jdt-mcp-server#49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
An mehreren Stellen wird
ASTParser.setResolveBindings(true)aufgerufen, abersetProject()fehlt. Laut JDT-Dokumentation (AST-002) liefertresolveBinding()dann null.Betroffene Stellen
CodeQualityTools.javaZeilen 89-92 und 211-214ConvertToLambdaRefactoring.javaZeile 97-100RenameRefactoring.javaZeile 429-432Fix
Gefunden von
Vogel (JDT API-Expertise)
Triage 2026-09-07: Fehlalarm, wird geschlossen
Alle sechs Stellen mit
setResolveBindings(true)rufen vorherparser.setSource(ICompilationUnit)auf (RenameRefactoring:479,CodeQualityTools:90/212,RefactoringTools:406,ConvertToLambdaRefactoring:98,ImportOrganizer:87).Laut JDT-Javadoc zu
ASTParser.setSource(ICompilationUnit): "This method automatically sets the project (and compiler options) based on the given compilation unit".setProject()ist nur beisetSource(char[])bzw.setSource(IClassFile)-losen Quellen nötig. Bindings sind hier also nicht null.Kein Code-Fix erforderlich.