| Summary: | [refactoring] Move instance method inserts argument at wrong position | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
| Component: | UI | Assignee: | Tobias Widmer <tobias_widmer> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | bmiller, martinae |
| Version: | 3.2 | ||
| Target Milestone: | 3.2 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 36032 | ||
| Bug Blocks: | |||
Filed related bug 108088 Fixed by fix for 36032 Added regression test MoveInstanceMethodTests#test36 verifying for RC3 verified |
I20050823-0800 class A { B fB; public void doit(String doitArg) { subroutine(1.2f); } public void subroutine(float subArg) { subsub(); } public void subsub() { } } class B { } - move doit(..) to fB -> compiles - move subroutine(..) to fB -> does not compile since subroutine's new parameter A a is at first position but the argument at the call site is at the second position Please fix and add a second test case where methods have 2 or more parameters.