Community
Participate
Working Groups
I have noticed 2 situations where "long" package names are split across multiple lines producing unreadable code. Case 1: import a.very.long.package.name.which.exceeds.the.format.length; Case 2: a.very.long.package.name.which.exceeds.the.format.length aVar; aVar = = (a.very.long.package.name.which.exceeds.the.format.length) invokeMethod(a.very.long.package.name.which.exceeds.the.format.length2.class); Both of them format to the following: import a. very. long. package. name. .... And I think you get the picture for the other case. I don't know about you but splitting package names like that doesn't make for very readable code. My only solution has been the lengthen my formatting line which has some other undesirable side effects.
Moved to JDT Core.
Post 2.0
This is related to bug 20672.
Ooops - sorry, typo, this is related to bug 20627. Forget 20672 (does not exist while I write this).
Resurrecting formatter issues in 2.1 stream.
Clearing resolution
*** Bug 20908 has been marked as a duplicate of this bug. ***
*** Bug 25896 has been marked as a duplicate of this bug. ***
*** Bug 25875 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.
*** Bug 33000 has been marked as a duplicate of this bug. ***
Resurrecting for 3.0
Reopening
This is addressed in the new formatter. Fixed and released in HEAD. Regression test added.
Verified.