| Summary: | [clean up] Code Clean Local Variable Declarations | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Nathan Reynolds <numeralnathan> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | deepakazad, markus.kell.r |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Nathan Reynolds
A Save Action (or a Clean Up) can probably work here and makes more sense than configuring the quick fix. Note that JDT can be extended with additional Clean ups and Save Actions. See http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Fguide%2Fjdt_api_contributing_a_cleanup.htm => Read as: you can write a clean up for your use (and maybe later provide a patch here for consideration in JDT) As mentioned in bug 367587, putting all local variable declarations at the start of a method is not a popular or even a recommended style. Hence, this clean up will not be added to JDT. (However, as mentioned in comment 1 you should be able to write your own Clean Up) |