Extract Interface nutzt String-Manipulation statt ASTRewrite #35
Labels
No labels
bug
build
enhancement
headless
P1-critical
P2-high
P3-medium
P4-low
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-tools/jdt-mcp-server#35
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
extractInterface()baut die Interface-Source manuell per StringBuilder zusammen und modifiziert die Klasse per String-indexOf/substring. Das ist fragil und kann bei komplexen Klassen-Deklarationen (Generics, mehrere Interfaces, Annotations) fehlschlagen.Betroffener Code
RefactoringTools.javaZeilen 852-1035Vorgeschlagener Fix
Nutze JDT
ASTRewriteAPI oder die interneExtractInterfaceRefactoringKlasse.Kontext
Identifiziert bei der Architektur-Analyse durch Agent jdt-gamma (Erich Gamma).
Gefixt in Branch
fix/43-refactoring-errors:ExtractInterfaceProcessor+ProcessorBasedRefactoringJavaPreferencesSettingsmit Headless-Fallback fürCodeGenerationSettingsCommits:
8084c7d,5d0e793