Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 199152

Summary: [formatter] Wrong wrap when just one long method arg is used
Product: [Eclipse Project] JDT Reporter: Lorenzo Donati <lorenzo.donati.bz>
Component: CoreAssignee: Mateusz Matela <mateusz.matela>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P5 CC: mateusz.matela
Version: 3.3   
Target Milestone: 4.5   
Hardware: PC   
OS: Windows XP   
Whiteboard: To be verified for 4.15 M1
Attachments:
Description Flags
A file with a class definition and complete bug description in its comments none

Description Lorenzo Donati CLA 2007-08-07 15:19:25 EDT
Created attachment 75573 [details]
A file with a class definition and complete bug description in its comments

Build ID: I20070625-1500

Steps To Reproduce:

The attached code will show the problem when formatted. Complete bug description and steps to reproduce written in the code as comments.

Brief description: it seems that the formatter is unable to wrap a method call when there is just one very long argument (no problem with two or more).

I remember I experienced this behaviour for rather a long time (since 3.1, if I remember well), but I didn't find the time to explore the issue with due attention (I was convinced it was my fault for not being able to set all those formatter options the right way). By now I'v grown quite convinced that there's a bug, since I didn't manage to find a way to make it's behaviour consistent (see the code attached).

Thanks a lot.
Lorenzo Donati
Comment 1 Lorenzo Donati CLA 2007-08-07 15:33:00 EDT
Comment on attachment 75573 [details]
A file with a class definition and complete bug description in its comments

VERY SORRY! I used the wrong file version!

The following comment:

>		/*- 
>		 * someVeryLongMethodNameHavingJustOneArgument(
>		 *      aVeryLongArgumentExpression);
>		 */

should read like this:

                 /*- 
		 * someVeryLongMethodNameHavingJustOneArgument(
		 *      aVeryLongArgumentTriggeringABugInEclipseFormatter);
		 */

Sorry again!
Comment 2 Frederic Fusier CLA 2008-08-18 08:07:52 EDT
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
Comment 3 Eclipse Genie CLA 2019-11-27 18:29:26 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Mateusz Matela CLA 2019-12-01 08:07:25 EST
This problem no longer occurs since the formatter redesign.

*** This bug has been marked as a duplicate of bug 303519 ***