Summary: | NamingConventions.suggestXXXNames should call suggestVariableNames() | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | David Audel <david_audel> | ||||
Component: | Core | Assignee: | David Audel <david_audel> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | jerome_lanneluc, markus.kell.r, srikanth_sankaran | ||||
Version: | 3.5 | ||||||
Target Milestone: | 3.5 M4 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
David Audel
2008-10-22 07:20:33 EDT
Other methods of NamingConventions should use new methods instead of deprecated methods. Created attachment 118352 [details]
Proposed fix
Released for 3.5M4. Tests added NamingConventionsTests#testSuggestGetterName009() NamingConventionsTests#testSuggestSetterName003() FYI: I just ran JDT/UI tests from 2 weeks ago (using the deprecated APIs) against HEAD of JDT/Core, and except for the expected changes from bug 38111 comment 12, everything stayed green :-). Verified for 3.5M4 using I20081208-1800 build |