Community
Participate
Working Groups
Consider a line like this: longObjectExpression.methodCall(foo, bar, baz); with "Line Wrapping -> Function Calls -> Arguments" configured as follows: Wrap only when necessary Indent on column Don't force split Now suppose that the call and its first argument, i.e. longObjectExpression.methodCall(foo, exceed the line limit all by themselves. Eclipse is currently formatting this as: longObjectExpression.methodCall( foo, Since the "indent on column" rule is forcing a long line anyway, the newline is simply unnecessary vertical whitespace. The first argument should appear on the method-call line unless "Force Split" is selected. Analogous problems occur with constructor calls, with constructor and method declarations, with 'throws' clauses everywhere, with enum arguments, etc.
See and vote for Bug 198074
what causes this: http://img505.imageshack.us/img505/4162/formatteryx2.gif if it's not a bug, how do i stop it?
Ownership has changed for the formatter, but I surely will not have enough time to fix your bug during the 3.5 development process, hence set its priority to P5. Please provide a patch if you definitely need the bug to be fixed in this version and I'll have a look at it... TIA
This problem no longer occurs after the formatter redesign. *** This bug has been marked as a duplicate of bug 303519 ***