Community
Participate
Working Groups
My preferred style is not an available configuration of the editor. (Braces aligned with the code they contain, not the structure they are subordinate to). It would also be nice if an emacs-like behavior with indenting were available. Additionally, it seems that generated code doesn't conform to indentation and line position preferences defined for the editor (although I've said that opening braces are on their own line, generated code puts them on the same line as the function or class declaration.)
How about splitting this into three separate bugs?
Formatter will be revisited deeply in the middle term, but unlikely before 2.0. Now if external contributors are willing to help, this might change.
I also prefer (Braces aligned with the code they contain, not the structure they are subordinate to) and it IS a big deal for most of my developers! We tend to deal in other developer's code and the formatter really works against us now.
Resurrecting formatter issues in 2.1 stream.
Clearing resolution
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
Reopening
This is addressed with the new code formatter. Unfortunately all options won't be expose immediately in the UI. Fixed and released in HEAD.
Verified.
