Community
Participate
Working Groups
i would like a few more options under Preferences->Java->Code Formatter to suit my somewhat bizzarre coding style: really compact assignment: for example, 'int x=1' instead of 'int x = 1' compact compares: 'if (x==1)' or 'if (x == 1)' compact boolean operations: 'if (true&&false)' or 'if (true && false)' compact casts: 'Element x = (Element)object' or 'Element x = (Element) object' compact arguments: 'foo(x,y)' or 'foo(x, y)' adding these would really make me happy.
Sounds doable with our new code formatter implementation...
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.
This is addressed in the new formatter. Fixed and released in HEAD. Regression test added.
Verified.
is there any way to manually set the options until a UI comes out?
The Jalopy Plugin for Eclipse will do all of this.
Jalopy development has been discontinued...bugs are not going to get fixed... features are not going to get added...unlike in eclipse!
and as i said before, jalopy is under the BSD liscense
you haven't said that in this bug report. The fact that it is BSD doesn't contradict what I said: "bugs are not going to get fixed...features are not going to get added...unlike in eclipse!"
>"bugs are not going to get fixed... >features are not going to get added... >unlike in eclipse!" I believe your comments are a bit misleading. Jalopy is an open source project. Although the original author(s) might not be supporting it anymore (in favor of their new commercial version), the code is still sitting on SourceForge for anyone to enhance/fix/modify as they see fit.
Then go ahead. Nothing prevents you from doing it. Eclipse is an open-source project after all.
Nobody has done any work on Jalopy for a long time and doesn't seem likely. However the same is definately not true for eclipse! My point is that bugs/enhancements are 1000% more likely to be addressed in Eclipse.