fix: catch IllegalArgumentException in field rename headless mode (#22) #23
No reviewers
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!23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/version-tool"
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
jdt_rename_elementwithFIELDstill throwsIllegalArgumentExceptiondespite the fix from #21setRenameGetters/Setters(false)only prevents co-renaming, but Eclipse still callsGetterSetterUtil.getSetterNameinternally duringcheckAllConditions(), which fails viaProjectScope.getNode()in headless modeIllegalArgumentExceptionfor field renames, creates a fresh refactoring instance, and falls back tocheckInitialConditionsonly (skipping the getter/setter name resolution code path)Test plan
preview=trueno longer throwsIllegalArgumentExceptionpreview=falseapplies correctlyIllegalArgumentExceptionfor non-field renames is still propagated🤖 Generated with Claude Code