fix: improve error reporting and inline method support (#43) #44
No reviewers
Labels
No labels
bug
build
enhancement
headless
P1-critical
P2-high
P3-medium
P4-low
refactoring
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-tools/jdt-mcp-server!44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/43-refactoring-errors"
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?
Summary
Addresses easy/medium issues from #43 (cross-module refactoring failures):
move_type,change_method_signature,inlinenow log full stack traces and show actual exception info instead of"null"whengetMessage()is emptygetRealErrors()now skips "potential match" warnings that incorrectly blocked interface method renames in headless modeInlineMethodRefactoringfallback —jdt_inlinenow supports both local variables and methods (previously only local variables)Not yet addressed (harder issues from #43)
move_typeunderlying NPE with MoveDescriptor in headless modechange_method_signatureNPE for interface methods with cross-module implementationsrename_elementMETHOD missing method-reference::updates in AST fallbackTest plan
jdt_inlineon a method → should inline instead of "No inlineable element"jdt_rename_elementon interface method → should proceed instead of "potential matches" errorjdt_move_typefailure → error message now shows actual exception, not just "null"jdt_change_method_signaturefailure → error shows exception type and cause🤖 Generated with Claude Code
3c9f63bddato5a0afc41a2