| Summary: | [encapsulate field] Encapsulate field refactoring ignores naming conventions | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Nils Kulk <n.kulk> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r, n.kulk, Olivier_Thomann |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Move to JDT/UI *** This bug has been marked as a duplicate of bug 252779 *** |
Build Identifier: 20100218-1602 When in the naming conventions "Qualify all generated field accesses with 'this.'" is switched off and a parameter prefix is configured, then encapsulate field generates a setter with 'this.' in the field reference and without prefix in the parameter. Reproducible: Always Steps to Reproduce: In the naming conventions configuration, switch off "Qualify all generated field accesses with 'this.'" and set the parameter prefix list to "a". Then, considering the following class, encapsulate the field bar: public class Foo { private String bar; } Then the generated setter is: public void setBar(String bar) { this.bar = bar; } Where the setter expected is: public void setBar(String aBar) { bar = aBar; }