Summary: | Java formatter enhancements | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Kirill Frolov <fkirill> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | arnijr |
Version: | 2.0 | ||
Target Milestone: | 3.0 M4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Kirill Frolov
2001-11-24 02:13:53 EST
Defer till post 2.0. Resurrecting formatter issues in 2.1 stream. Clearing resolution An additional option I would like is for the formatter to reorganise methods and fields according to the Java Coding Guidelines: 1. Static variable field declarations 2. Instance variable field declarations 3. Static initializer 4. Static member inner class declarations 5. Static method declarations 6. Instance initializer 7. Instance constructor declarations 8. Instance member inner class declarations 9. Instance method declarations *** Bug 27111 has been marked as a duplicate of this bug. *** We need to clear 2.1 bug reports that won't be addressed before 2.1. The new implementation is still in the works. Therefore we cannot include it for 2.1. Not enough testing and we need to polish the preferences. This will be address for 2.2 as stated in the JDT/Core plan. Resurrecting for 3.0 Reopen for 3.0 consideration. Please look at the new formatter options when they are exposed in the UI (between M4 and M5). If you believe that we should add more options, open one PR per request. The sorting of compilation unit elements is already available. See Source>Sort members. This is not a code formatter feature. Verified. i'd like this from the request to be implemented: 9. Should formatter surround simple body with braces (always/never/if on the next line) sorry didnt realize this bug is closed... reopen new one for this The rule we try to follow is that the code formatter doesn't change the code. Adding braces is changing the code. So it won't be done. |